I read the man pace ahead of time, and noticed that little quirk. i guess i understand why it might copy each link to the inode as a seperate file. It makes me wonder though if there's not a better tool for the job of replicating a filesystem to another disk aside from dd'ing the whole thing.
<br><br><div><span class="gmail_quote">On 7/21/07, <b class="gmail_sendername">Charles Steinkuehler</b> <<a href="mailto:charles@steinkuehler.net">charles@steinkuehler.net</a>> wrote:</span><blockquote class="gmail_quote" style="border-left: 1px solid rgb(204, 204, 204); margin: 0pt 0pt 0pt 0.8ex; padding-left: 1ex;">
-----BEGIN PGP SIGNED MESSAGE-----<br>Hash: SHA1<br><br>Billy Crook wrote:<br>> That must be exactly it. I remember when I formatted crypt, I did specifiy<br>> options. Whereas when I formatted crypt2, I did not. Can't check to make
<br>> sure though. crypt2 will be in a bank vault for 6 months. Crypt3 is in the<br>> works though. Should be ready to play with by next Friday. Im just glad it<br>> wasn't a filesystem error.<br><br>The other thing that can cause this are hard links, which are *NOT*
<br>copied by default when using the -a switch to rsync. You have to<br>specify --hard-links or you wind up with N actual copies of any<br>hardlinked files, instead of one file and N inodes.<br><br>- --<br>Charles Steinkuehler
<br><a href="mailto:charles@steinkuehler.net">charles@steinkuehler.net</a><br>-----BEGIN PGP SIGNATURE-----<br>Version: GnuPG v1.4.0 (MingW32)<br>Comment: Using GnuPG with Mozilla - <a href="http://enigmail.mozdev.org">http://enigmail.mozdev.org
</a><br><br>iD8DBQFGomiNLywbqEHdNFwRAmibAKDS5RixuHos1h0on7fxQRQZTQTPnwCggAv5<br>aeotZsbZrSWZOCo5jcXZHFk=<br>=kYE+<br>-----END PGP SIGNATURE-----<br></blockquote></div><br>