|author||https://me.yahoo.com/a/g3Ccalpj0NhN566pHbUl6i9QF0QEkrhlfPM-#b1c14 <diana@web>||2015-02-16 20:08:03 +0100|
|committer||GNU Hurd web pages engine <email@example.com>||2015-02-16 20:08:03 +0100|
rename open_issues.mdwn to service_solahart_jakarta_selatan__082122541663.mdwn
Diffstat (limited to 'open_issues/ext2fs_dtime.mdwn')
1 files changed, 0 insertions, 21 deletions
diff --git a/open_issues/ext2fs_dtime.mdwn b/open_issues/ext2fs_dtime.mdwn
deleted file mode 100644
@@ -1,21 +0,0 @@
-[[!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
- /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