I reported this earlier, for 2.2.10-ac10, so I thought I'd try
2.2.11pre2, and I get the same behavior, namely the inode numbers on
vfat partitions change between boots. I use tar for incremental
backups and when it notices an inode change between backups it assumes
a rename and does a backup. Needless to say, the fact that vfat
partitions don't have constant inode #'s plays havoc with my backup
scheme. This didn't happen with 2.0.36 and 2.2.10-ac10 is the first
2.2.x series kernel I've used.
Is this "varying inode" behavior on vfat drives going to be the
standard now or is something wrong with my setup?
Thanks,
Gary Hennigan
-
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@vger.rutgers.edu
Please read the FAQ at http://www.tux.org/lkml/