summaryrefslogtreecommitdiff
diff options
context:
space:
mode:
authorSamuel Thibault <samuel.thibault@ens-lyon.org>2026-09-27 21:02:49 +0200
committerSamuel Thibault <samuel.thibault@ens-lyon.org>2026-09-27 21:02:49 +0200
commita9ccf942bdafbb1a84df186095937e811a390a5d (patch)
treee8c0f1f0d7a9574dc432f6200ef599732b58a8f8
parent4624878bfea9e3f257820accd2a1e23b31ca5fe1 (diff)
ext2 orphan list was implemented
-rw-r--r--faq/fsck.mdwn4
-rw-r--r--open_issues/ext2fs_dtime.mdwn21
2 files changed, 3 insertions, 22 deletions
diff --git a/faq/fsck.mdwn b/faq/fsck.mdwn
index 5658a799..c05685f6 100644
--- a/faq/fsck.mdwn
+++ b/faq/fsck.mdwn
@@ -28,7 +28,9 @@ Quite a few of them are actually benign:
[...]
Free inodes count wrong (880891, counted=880909).
-see [[open_issues/ext2fs_dtime]]
+This was fixed on september 2026 by implementing the orphan list, available along journaling support:
+
+https://lists.gnu.org/archive/html/bug-hurd/2026-09/msg00079.html
/dev/hd0s1: i_file_acl_hi for inode 81872 (/proc) is 32, shoud be 0.
diff --git a/open_issues/ext2fs_dtime.mdwn b/open_issues/ext2fs_dtime.mdwn
deleted file mode 100644
index 5cb5fb7b..00000000
--- a/open_issues/ext2fs_dtime.mdwn
+++ /dev/null
@@ -1,21 +0,0 @@
-[[!meta copyright="Copyright © 2014 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.