A while back my system didn't get unmounted so I had to fsck
and fsck found a zero dtime Inode and it said it fixed it. But just for
fun I set tune2fs so that my system would force a fsck at every boot.
Now every time I boot up fsck finds 1 or more zero dtime inodes and it
says it repairs them. I set in my scripts for umount to do verbose mode
to make sure the drive was getting unmounted and it is. I also ran the
bad blocks program and it found no bad blocks. I also tried to do a
readonly e2defrag and it says error seeking to end of filesystem. I
checked fdisk to make sure there was no over lapping in partions and
theres not. I just cant figure out why fsck always on every boot finds
zero dtime inodes?
/dev/hdb1 * Start 1 End 1024 Blocks 7741408+ 83 Linux
/dev/hdb2 1025 2651 12300120 f Win95 Ext'd (LBA)
/dev/hdb5 1025 2651 12300088+ b Win95 FAT32