From 49a086299e047b18280457b654790ef4a2e5abfa Mon Sep 17 00:00:00 2001 From: Samuel Thibault Date: Wed, 18 Feb 2015 00:58:35 +0100 Subject: Revert "rename open_issues.mdwn to service_solahart_jakarta_selatan__082122541663.mdwn" This reverts commit 95878586ec7611791f4001a4ee17abf943fae3c1. --- open_issues/e2fsck_i_file_acl_hi.mdwn | 40 +++++++++++++++++++++++++++++++++++ 1 file changed, 40 insertions(+) create mode 100644 open_issues/e2fsck_i_file_acl_hi.mdwn (limited to 'open_issues/e2fsck_i_file_acl_hi.mdwn') diff --git a/open_issues/e2fsck_i_file_acl_hi.mdwn b/open_issues/e2fsck_i_file_acl_hi.mdwn new file mode 100644 index 00000000..d891ac6e --- /dev/null +++ b/open_issues/e2fsck_i_file_acl_hi.mdwn @@ -0,0 +1,40 @@ +[[!meta copyright="Copyright © 2010, 2011 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]]."]]"""]] + +IRC, unknown channel, unknown date. + + something's broken in ext2, fsck, or the like + /dev/hd0s1: i_file_acl_hi for inode 81872 (/proc) is 32, shoud be 0. + youpi: the other problem is probably related to http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=526524 + i'll just check when it is fixed + youpi: I've seen a lot of these fsck errors since the upgrade to 1.41.x + youpi: seems to happen whenever a passive translator is still active while the machine reboots + antrik: ho, so in my example this could be related to procfs then + Duck: don't know... I got it with various terminal-related nodes + other translators get terminated before ext2 it seems, so the problem doesn't happen there + unless the machine crashes of course + ah, right, it told you that it's the /proc node :-) + was it the only node it complained about? + Duck: ^ + antrik: yes, the only one + so it's most probably i + t + but currently i don't have much translators around besides the base install + that's strange... my theory about translators active at reboot seems wrong then + well, maybe procps is not behaving properly + procfs* + youpi: I doubt it. I regularily get the same issue with various term nodes; and when the machine crashes rather than rebooting cleanly, many other nodes as well + k + but it's always passive translator nodes + +This is due to an erroneous read/write from e2fsck, see +. + +See [[!debbug 760275]] -- cgit v1.2.3