# rsync -rvnc --delete /brick0 /brick1
I've confirmed that separate devices are mounted to /brick0 and /brick1. What I'm seeing for ~ 20 minutes now is only the device mounted at brick0 is being accessed, and yet I'm seeing piles of files (verbose option) being listed.
I'd expect that there'd be some back and forth as the checksum comparison happens almost simultaneously. Any ideas how this ought to work? Is rsync caching the checksums for brick0, and then it'll go compute checksums on brick1 and compare?
Maybe I should use diff -qr because this is just too much verbosity anyway. I don't need every file listed. I only want to know if there are any files that are different (deleted), but I don't know if I get any delete notification from rsync without -v.
On 08/30/2015 10:30 AM, Chris Murphy wrote:
# rsync -rvnc --delete /brick0 /brick1
I've confirmed that separate devices are mounted to /brick0 and /brick1. What I'm seeing for ~ 20 minutes now is only the device mounted at brick0 is being accessed, and yet I'm seeing piles of files (verbose option) being listed.
Try: rsync -rvnc --delete /brick0/ /brick1/
On Sun, Aug 30, 2015 at 1:01 PM, Gordon Messmer gordon.messmer@gmail.com wrote:
On 08/30/2015 10:30 AM, Chris Murphy wrote:
# rsync -rvnc --delete /brick0 /brick1
I've confirmed that separate devices are mounted to /brick0 and /brick1. What I'm seeing for ~ 20 minutes now is only the device mounted at brick0 is being accessed, and yet I'm seeing piles of files (verbose option) being listed.
Try: rsync -rvnc --delete /brick0/ /brick1/
So it was seeing them as 100% different because... shit.
On Sun, Aug 30, 2015 at 01:17:00PM -0600, Chris Murphy wrote:
On Sun, Aug 30, 2015 at 1:01 PM, Gordon Messmer gordon.messmer@gmail.com wrote:
On 08/30/2015 10:30 AM, Chris Murphy wrote:
# rsync -rvnc --delete /brick0 /brick1
I've confirmed that separate devices are mounted to /brick0 and /brick1. What I'm seeing for ~ 20 minutes now is only the device mounted at brick0 is being accessed, and yet I'm seeing piles of files (verbose option) being listed.
Try: rsync -rvnc --delete /brick0/ /brick1/
So it was seeing them as 100% different because... shit.
Interesting, I do not understand this behaviour either. Anyone care to elaborate?
$ mkdir -p foo{1,2}/bar $ touch foo{1,2}/{bla,bar/baz} $ echo > foo1/bla $ dirdiff foo? # dirdiff is a wrapper around rsync -rvnc --delete sending incremental file list foo1/ foo1/bla foo1/bar/ foo1/bar/baz
sent 168 bytes received 30 bytes 396.00 bytes/sec total size is 1 speedup is 0.01 (DRY RUN) $ dirdiff foo?/ sending incremental file list bla
sent 150 bytes received 20 bytes 340.00 bytes/sec total size is 1 speedup is 0.01 (DRY RUN)
On Mon, Aug 31, 2015 at 02:25:42AM +0200, Suvayu Ali wrote:
On Sun, Aug 30, 2015 at 01:17:00PM -0600, Chris Murphy wrote:
On Sun, Aug 30, 2015 at 1:01 PM, Gordon Messmer gordon.messmer@gmail.com wrote:
On 08/30/2015 10:30 AM, Chris Murphy wrote:
# rsync -rvnc --delete /brick0 /brick1
I've confirmed that separate devices are mounted to /brick0 and /brick1. What I'm seeing for ~ 20 minutes now is only the device mounted at brick0 is being accessed, and yet I'm seeing piles of files (verbose option) being listed.
Try: rsync -rvnc --delete /brick0/ /brick1/
So it was seeing them as 100% different because... shit.
Interesting, I do not understand this behaviour either. Anyone care to elaborate?
[...chomp...chomp...chomp...]
$ dirdiff foo?/
Forget it, my brain started working after I hit send. Writing the above as the following makes the distinction clear.
$ dirdiff foo1/ foo2
Pff!
On Sun, Aug 30, 2015 at 6:29 PM, Suvayu Ali fatkasuvayu+linux@gmail.com wrote:
On Mon, Aug 31, 2015 at 02:25:42AM +0200, Suvayu Ali wrote:
On Sun, Aug 30, 2015 at 01:17:00PM -0600, Chris Murphy wrote:
On Sun, Aug 30, 2015 at 1:01 PM, Gordon Messmer gordon.messmer@gmail.com wrote:
On 08/30/2015 10:30 AM, Chris Murphy wrote:
# rsync -rvnc --delete /brick0 /brick1
I've confirmed that separate devices are mounted to /brick0 and /brick1. What I'm seeing for ~ 20 minutes now is only the device mounted at brick0 is being accessed, and yet I'm seeing piles of files (verbose option) being listed.
Try: rsync -rvnc --delete /brick0/ /brick1/
So it was seeing them as 100% different because... shit.
Interesting, I do not understand this behaviour either. Anyone care to elaborate?
[...chomp...chomp...chomp...]
$ dirdiff foo?/
Forget it, my brain started working after I hit send. Writing the above as the following makes the distinction clear.
$ dirdiff foo1/ foo2
Pff!
Yes, it's because of this "A trailing slash on the source changes this behavior to avoid creating an additional directory level at the destination." So without the trailing / it was creating brick0 in brick1 (for me).
On 08/30/2015 08:25 PM, Suvayu Ali wrote:
So it was seeing them as 100% different because... shit. Interesting, I do not understand this behaviour either. Anyone care to elaborate?
Simple ... RTFM ...
From the man page for rsync:
A trailing slash on the source changes this behavior to avoid creating an additional directory level at the destination. You can think of a trailing / on a source as meaning "copy the contents of this directory" as opposed to "copy the directory by name", but in both cases the attributes of the containing directory are transferred to the contain‐ ing directory on the destination. In other words, each of the follow‐ ing commands copies the files in the same way, including their setting of the attributes of /dest/foo:
rsync -av /src/foo /dest rsync -av /src/foo/ /dest/foo ...
On Sun, Aug 30, 2015 at 06:52:20PM -0600, Chris Murphy wrote:
On Sun, Aug 30, 2015 at 6:29 PM, Suvayu Ali fatkasuvayu+linux@gmail.com wrote:
On Mon, Aug 31, 2015 at 02:25:42AM +0200, Suvayu Ali wrote:
On Sun, Aug 30, 2015 at 01:17:00PM -0600, Chris Murphy wrote:
On Sun, Aug 30, 2015 at 1:01 PM, Gordon Messmer gordon.messmer@gmail.com wrote:
On 08/30/2015 10:30 AM, Chris Murphy wrote:
# rsync -rvnc --delete /brick0 /brick1
I've confirmed that separate devices are mounted to /brick0 and /brick1. What I'm seeing for ~ 20 minutes now is only the device mounted at brick0 is being accessed, and yet I'm seeing piles of files (verbose option) being listed.
Try: rsync -rvnc --delete /brick0/ /brick1/
So it was seeing them as 100% different because... shit.
Interesting, I do not understand this behaviour either. Anyone care to elaborate?
[...chomp...chomp...chomp...]
$ dirdiff foo?/
Forget it, my brain started working after I hit send. Writing the above as the following makes the distinction clear.
$ dirdiff foo1/ foo2
Pff!
Yes, it's because of this "A trailing slash on the source changes this behavior to avoid creating an additional directory level at the destination." So without the trailing / it was creating brick0 in brick1 (for me).
I always fall prey to this subtle distinction, specially since the shell always completes directories with the trailing slash. Makes me wonder, would it be worthwhile to file an RFE against bash-completion etc, to consider foo1 and foo1/ as separate completion candidates when completing rsync arguments?
Undoubtedly this will lead to ugly code though.
Cheers,
On Mon, Aug 31, 2015 at 11:52:52AM +0200, Suvayu Ali wrote:
I always fall prey to this subtle distinction, specially since the shell always completes directories with the trailing slash. Makes me wonder, would it be worthwhile to file an RFE against bash-completion etc, to consider foo1 and foo1/ as separate completion candidates when completing rsync arguments?
Done: https://bugzilla.redhat.com/show_bug.cgi?id=1258410
-
Chris Murphy -
Derrik Walker v2.0 -
Gordon Messmer -
Suvayu Ali