Messages in this thread | | | Date | Tue, 4 Aug 1998 17:24:55 -0400 | From | "Theodore Y. Ts'o" <> | Subject | Re: Irritating ext2fs corruption |
| |
Date: Tue, 4 Aug 1998 12:59:12 +0200 From: Jan Niehusmann <post002@gondor.com>
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.
It's important to distinguish between "an uncleanly shutdown system" and "an uncleanly unmounted filesystem". Even if you do a clean shutdown, if some process refuses to die and has a deleted file open, that one particular filesystem may not have been cleanly unmounted. It's easy to miss the warning message during the shutdown sequence, since the machine quickly resets itself after that and starts to reboot the system.
- Ted
- 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
| |