It's probably not new in 2.1.* - I get 'zero dtime' even with 2.0.35.
I don't know how they are generated, as I don't normally fsck unless
I had an unclean shutdown (and then it's normal to get some fs errors).
But every now and then fsck gets forced by 'maximum mount count reached'.
I assume that these fsck are not expected to find any fs problems - but
they very often report zero dtime errors.
May it be that deleted inodes are not reliably written to disk on unmount?
Jan
-- PGP-Key-ID: 1024/DAD29745 1994/09/02 Jan Niehusmann <jan@gondor.com> Fingerprint: C9 99 62 ED 57 A3 13 74 75 33 00 7B D8 0C 14 17- 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