Clint Olsen
2012-Jun-05 21:02 UTC
Fwd: --link-dest does not appear to be linking on Cygwin
Hi: I have attempted to following some instructions to use --link-dest in order to preserve space for multiple backups. I'm using rsync on Cygwin with a NAS (ext4) which does support hard-links on the filesystem. I've written a short program that does attempt to create a hard-link on this NAS from Cygwin and it does look to be working. If I run ls -li on the NAS the inodes are the same. However, on Cygwin the inodes returned are not. I assumed that what's important is that the NAS handles the hard-links correctly. I checked the archives and it looks like a common mistake is inconsistent usage of the trailing backslash. My usage looks something like: % rsync -aP --delete --delete-excluded --exclude-from=/home/Nancy/.rsync/exclude --link-dest=/cygdrive/f/macki/current/ Nancy /cygdrive/f/macki/incomplete-back-2012-06-05T13:53:51 I'm running this from "/cygwin/c/Documents and Settings/" directory, and the directory under the symlink "current" is "Nancy". Is there a way to tell if rsync thinks it's found a match and attempting to link? Thanks, -Clint
-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 - --itemize-changes would be the first place to start. Also, see if you can make a hard link on your NAS. Just because the underlying ext4 supports it doesn't mean that your network mount does. Try something like: cd /cygdrive/f/macki touch testfile ln testfile testfile2 ls -ls testfile testfile2 They should both have the same inode number. On 06/05/12 17:02, Clint Olsen wrote:> Hi: > > I have attempted to following some instructions to use --link-dest > in order to preserve space for multiple backups. I'm using rsync > on Cygwin with a NAS (ext4) which does support hard-links on the > filesystem. I've written a short program that does attempt to > create a hard-link on this NAS from Cygwin and it does look to be > working. If I run ls -li on the NAS the inodes are the same. > However, on Cygwin the inodes returned are not. I assumed that > what's important is that the NAS handles the hard-links correctly. > > I checked the archives and it looks like a common mistake is > inconsistent usage of the trailing backslash. My usage looks > something like: > > % rsync -aP --delete --delete-excluded > --exclude-from=/home/Nancy/.rsync/exclude > --link-dest=/cygdrive/f/macki/current/ Nancy > /cygdrive/f/macki/incomplete-back-2012-06-05T13:53:51 > > I'm running this from "/cygwin/c/Documents and Settings/" > directory, and the directory under the symlink "current" is > "Nancy". > > Is there a way to tell if rsync thinks it's found a match and > attempting to link? > > Thanks, > > -Clint- -- ~*-,._.,-*~'`^`'~*-,._.,-*~'`^`'~*-,._.,-*~'`^`'~*-,._.,-*~'`^`'~*-,._.,-*~ 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/ iEYEARECAAYFAk/OdL4ACgkQVKC1jlbQAQe9EgCgqYVuiaHi0MTD6MZjISt539aF 7SMAoOJu8y508ZGMySbqgkch6Mellg3g =DBkr -----END PGP SIGNATURE-----