diff options
| -rw-r--r-- | open_issues/ext2fs_dtime.mdwn | 21 |
1 files changed, 21 insertions, 0 deletions
diff --git a/open_issues/ext2fs_dtime.mdwn b/open_issues/ext2fs_dtime.mdwn new file mode 100644 index 00000000..592f1525 --- /dev/null +++ b/open_issues/ext2fs_dtime.mdwn @@ -0,0 +1,21 @@ +[[!meta copyright="Copyright © 2010, 2012 Free Software Foundation, Inc."]] + +[[!meta license="""[[!toggle id="license" text="GFDL 1.2+"]][[!toggleable +id="license" text="Permission is granted to copy, distribute and/or modify this +document under the terms of the GNU Free Documentation License, Version 1.2 or +any later version published by the Free Software Foundation; with no Invariant +Sections, no Front-Cover Texts, and no Back-Cover Texts. A copy of the license +is included in the section entitled [[GNU Free Documentation +License|/fdl]]."]]"""]] + +[[!tag open_issue_hurd]] + + /dev/hd0s1: Deleted inode 95849 has zero dtime. FIXED. + +This is actually sorta benign. What typically happens is that one upgrades e.g. +a library, and there are still some processes using it (e.g. because it's libc). +The library file is thus kept on the filesystem, so as to be able to load parts +of it on demand. The file is thus marked as deleted, but the deletion hasn't +been effective yet, thus dtime being zero. e2fsck notices this and finishes +deleting the file. To really fix this, we would probably have to really unmount +the filesystem. |