I have been getting inode with zero dtime on fsck-ing my root partition. As far
as I can tell, the system is shutted down cleanly and the filesystem is marked
'clean'. However, upon forcing a fcsk with '-f', there are inodes with zero
dtime.
After mucking around a bit, I found that it's related to ldconfig.
Here is what I did to reproduce inodes with zero dtime:
. boot up into single user mode, making sure the filesystem is clean with
'fsck -af'.
. Run "debugfs /dev/hda?", type "stat /etc/ld.so.cache" to find its inode
number.
. Run "ldconfig" which generates a new ld.so.cache. (/etc/ld.so.cache is
mmapped)
. Run "mount -o remount,ro /", followed by "fsck -f /dev/hda?" shows
an inode with zero dtime. The inode is that of /etc/ld.so.cache before
ldconfig is run.
I am using ldconfig from ld.so-1.9.9, linux 2.1.117 & glibc-2.0.7pre5.
Can anybody see what's wrong?
Thanks, Delman
-
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.altern.org/andrebalsa/doc/lkml-faq.html