Changing permissions on existing backup source
kmk at sanitarium.net
Thu Jan 2 11:23:50 MST 2014
-----BEGIN PGP SIGNED MESSAGE-----
Yep, if you change 1 you change the hard links in all of them.
On 01/02/2014 06:09 AM, Charles Marcus wrote:
> On 2014-01-01 1:12 PM, Kevin Korb <kmk at sanitarium.net> wrote:
>> The files will not be transferred but they will be stored
>> separately as new versions of the file even if the content is the
> Ok, so, 'stored separately' = take up additional space? which is
> what I want to avoid.
>> Permissions are per inode not directory entry so you can't have
>> old and new permissions without breaking the hard link
> Yeah, this is why I asked... thx...
>> The easiest solution is to just do the same chmod on the most
>> recent backup before running the next backup.
> Ah, that should work perfectly...
> So, just to make sure I understand, when I change the perms on the
> most recent backup, if I were to go back and look at any of the
> previous backups before that one, any files in those older backups
> that contain files that are hard-linked in the most recent backup
> would reflect the new permissions too, right?
> Best regards,
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.22 (GNU/Linux)
Comment: Using GnuPG with Thunderbird - http://www.enigmail.net/
-----END PGP SIGNATURE-----
More information about the rsync