Messages in this thread | | | Date | Thu, 10 Jul 1997 23:16:27 -0400 | From | "Theodore Y. Ts'o" <> | Subject | Re: PATCH to pre-patch-2.1.45: clean_inode needs to reset i_writecount |
| |
Date: Thu, 10 Jul 1997 16:07:02 -0700 (PDT) From: Linus Torvalds <torvalds@transmeta.com>
This _does_ result in "dtime not zero" messages from fsck (which runs at each boot), but that's actually because the ext2 "dtime" field is simply broken. So you should actually not worry about that message (but anything else would be worrysome..).
What don't you like about the semantics of the dtime field? It's "deletion" time, not "unlink" time. So the time in that field is when the inode is actually deallocated, not when it is unlinked from the directory hierarchy. This causes warnings during an unclean shutdown, but you have to run fsck after an unclean shutdown anyway, so it's no big deal.
- Ted
| |