https://bugzilla.samba.org/show_bug.cgi?id=11101
Bug ID: 11101
Summary: support writing to devices
Product: rsync
Version: 3.0.6
Hardware: All
OS: All
Status: NEW
Severity: normal
Priority: P5
Component: core
Assignee: wayned at samba.org
Reporter: jpyeron at pdinc.us
QA Contact: rsync-qa at samba.org
see https://bugzilla.redhat.com/show_bug.cgi?id=1193654
when rsyncing to a device, it is important to not delete the device node.
patch on redhat bugzilla.
--
You are receiving this mail because:
You are the QA Contact for the bug.
https://bugzilla.samba.org/show_bug.cgi?id=11101 --- Comment #1 from Jason Pyeron <jpyeron at pdinc.us> --- this is https://git.samba.org/?p=rsync-patches.git;a=blob;f=write-devices.diff using it in production now -- You are receiving this mail because: You are the QA Contact for the bug.
samba-bugs at samba.org wrote:> https://bugzilla.samba.org/show_bug.cgi?id=11101 > > --- Comment #1 from Jason Pyeron <jpyeron at pdinc.us> --- > this is > > https://git.samba.org/?p=rsync-patches.git;a=blob;f=write-devices.diff > > using it in production now >I'm am probably confused, but it looks like this patch doesn't copy the inode (device-inode), but is intended to copy the contents of a device? So if you did "rsync [options] /dev /dev2", instead of recreating or making a copy of "/dev", it would try to read every device in /dev and copy the contents to files(?) in /dev2? So "rsync [op] /dev/zero /dev2/zero" would not complete until whatever device "/dev2" is on, fills up, no? Why would you use 'rsync' to copy the contents of a device? Seems like it would be more efficient to do something like "cat /dev/zero >/dev2/zero", or better, use 'dd' which was designed for things like copying raw contents to a target. This seems like a potentially dangerous operation, since, in generally, how would rsync know when to stop? I.e. in the case of copy the contents of /dev/zero, even if you copied the contents to "/dev/null", how would rsync know when to stop? Wouldn't it go on forever?
https://bugzilla.samba.org/show_bug.cgi?id=11101 --- Comment #2 from Michal Ruprich <mruprich at redhat.com> --- I see that the write-devices.diff is in the rsync-patches-3.1.3.tar.gz but this bug is still in NEW state. Does that mean that the patch should not be used? What is the relationship between the rsync.git and rsync-patches.git? Thanks. -- You are receiving this mail because: You are the QA Contact for the bug.
https://bugzilla.samba.org/show_bug.cgi?id=11101 --- Comment #3 from Jason Pyeron <jpyeron at pdinc.us> --- the patches repo is where unmerged patches are tracked, stored, and re-baselined. Not sure how to tickle Wayne Davison to test it. It has worked very nicely here. -- You are receiving this mail because: You are the QA Contact for the bug.
https://bugzilla.samba.org/show_bug.cgi?id=11101
Wayne Davison <wayne at opencoder.net> changed:
What |Removed |Added
----------------------------------------------------------------------------
Resolution|--- |FIXED
Status|NEW |RESOLVED
--- Comment #4 from Wayne Davison <wayne at opencoder.net> ---
I've refined the old write-devices.diff from the patches repo and included
it
for the upcoming release.
--
You are receiving this mail because:
You are the QA Contact for the bug.
Hello all, I'm trying to copy a whole block device to another server. My issue is that I'm not able to write to a block device. The special file is overwritten by the normal file. I'm using rsync 3.1.3 on both servers, and I tried some commands: #rsync --bwlimit=100k -vvPz --copy-devices /dev/sdb root at 10.144.162.85:/dev/sdd #rsync --bwlimit=100k -vvPz --copy-devices --inplace /dev/sdb root at 10.144.162.85:/dev/sdd #rsync --bwlimit=100k -vvPz --copy-devices --inplace --devices /dev/sdb root at 10.144.162.85:/dev/sdd None of the commands worked well for me. Il giorno dom, 05/04/2020 alle 18.45 +0000, just subscribed for rsync- qa from bugzilla via rsync ha scritto:> https://bugzilla.samba.org/show_bug.cgi?id=11101 > > Wayne Davison <wayne at opencoder.net> changed: > What |Removed |Added--------------- > ----------------------------------------------------------- > -- Resolution| > - > -- |FIXED Status|NEW > |RESOLVED > --- Comment #4 from Wayne Davison <wayne at opencoder.net> ---I've > refined the old write-devices.diff from the patches repo and included > itfor the upcoming release.I cannot use the --write-devices option I cannot understand if the 3.1.3 contain the write-devices option or if I have to apply this patch. Can someone help me understanding the problem? Regards Ambrogio -------------- next part -------------- An HTML attachment was scrubbed... URL: <http://lists.samba.org/pipermail/rsync/attachments/20200424/45b7c8a4/attachment.htm>