rsync 3.0.x breaks behaviour of --one-file-system --relative --delete

[Kevin Korb]

-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1

Note that there is no mention of deletions in there only what rsync will
create and copy.  Rsync -x will not recurse into mount points.  It will
not do anything with stuff that is inside of another mount point
including deleting that stuff on the target.  The old behavior of
deleting stuff was a bug.  It was corrected.

I am not sure why repeating the option causes deletes but I can confirm
that it does.  This may be an additional occurrence of the bug from
before or it may be what was intended I am uncertain.

On 09/07/11 07:07, Simon Matter wrote:
> The old behavior was the bug.  3.0.6 fixed it.
> IOW, you were exploiting a bug without knowing it.
> 
>> I don't understand this. The manpage says
> 
>> %<
>> If  this  option is repeated, rsync omits all mount-point directories from
>> the copy. Otherwise, it includes an empty directory at each mount-point it
>> encounters (using the attributes of the mounted directory because those of
>> the underlying mount-point directory are inaccessible).
>> %<
> 
>> In other words, with -xx the mount point directory is not added to the
>> list and with --delete, it means the directory is correctly deleted on the
>> destination side.
> 
>> Then, with only -x, that's "Otherwise, it includes an empty directory at
>> each mount-point it encounters". Now, if it does so, with --delete, it
>> should also result in a empty directory on the destination side.
> 
>> Please note that -xx does exactly what it says, but -x does not!
> 
>> What did I miss?
> 
>> Thanks,
>> Simon
> 
> 
> On 09/06/11 18:27, Simon Matter wrote:
>>>>>> -----BEGIN PGP SIGNED MESSAGE-----
>>>>>> Hash: SHA1
>>>>>>
>>>>>> https://bugzilla.samba.org/show_bug.cgi?id=6240
>>>>>
>>>>> Oops, I have checked bugzilla.samba.org but _before_ I realized it has
>>>>> something to do with --one-file-system.
>>>>>
>>>>> Sorry for the noise - of course the RedHat BZ still applies to them :)
>>>>
>>>> Well, now I just looked a bit closer, did you say the bug should be
>>>> fixed?
>>>> As I understand the BZ you mention should be fixed in 3.0.6, which is
>>>> what
>>>> RHEL5.7 ship. And as I mentioned, I have built 3.0.8 from source and it
>>>> has the same bug for me, and 3.0.8 is the latest stable.
>>>>
>>>> Anyone cares to check this out on his on box?
>>>>
>>>> Thanks,
>>>> Simon
> 
>>

- -- 
~*-,._.,-*~'`^`'~*-,._.,-*~'`^`'~*-,._.,-*~'`^`'~*-,._.,-*~'`^`'~*-,._.,-*~
	Kevin Korb			Phone:    (407) 252-6853
	Systems Administrator		Internet:
	FutureQuest, Inc.		Kevin at FutureQuest.net  (work)
	Orlando, Florida		kmk at sanitarium.net (personal)
	Web page:			http://www.sanitarium.net/
	PGP public key available on web site.
~*-,._.,-*~'`^`'~*-,._.,-*~'`^`'~*-,._.,-*~'`^`'~*-,._.,-*~'`^`'~*-,._.,-*~
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v2.0.17 (GNU/Linux)
Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org/

iEYEARECAAYFAk5njPUACgkQVKC1jlbQAQcZHQCg/5bEZELPchpBXw5q38ZXuhga
mYwAniSmiVav2jomwgluMlakrs6s8gUB
=yTiV
-----END PGP SIGNATURE-----