> > Actually no. Statement 2 for me is important in terms of archive > correctness. With my "archiver" program Mksquashfs, if the two files > are the same, and filesystem says they're hardlinks, I make them > hardlinks in the Squashfs filesystem, otherwise they're stored as > duplicates (same data, different inode). Doesn't matter much in > terms of storage overhead, but it does matter if two files become > one, or vice versa. statement 2 was "all files that are hardlinks can be found with ino/dev pairs". How would files become one if accidentally the kernel shows a hardlinked file as 2 separate files in terms of inode nr or device? -- if you want to mail me at work (you don't), use arjan (at) linux.intel.com Test the interaction between Linux and your BIOS via http://www.linuxfirmwarekit.org - To unsubscribe from this list: send the line "unsubscribe linux-fsdevel" in the body of a message to majordomo@xxxxxxxxxxxxxxx More majordomo info at http://vger.kernel.org/majordomo-info.html
