[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-Id: <20130121020126.75BB911FC76@bugzilla.kernel.org>
Date: Mon, 21 Jan 2013 02:01:26 +0000 (UTC)
From: bugzilla-daemon@...zilla.kernel.org
To: linux-ext4@...r.kernel.org
Subject: [Bug 40822] EXT4-fs error (device dm-4): ext4_lookup:1044: inode
#3308277: comm rm: deleted inode referenced: 3058008
https://bugzilla.kernel.org/show_bug.cgi?id=40822
Theodore Tso <tytso@....edu> changed:
What |Removed |Added
----------------------------------------------------------------------------
CC| |tytso@....edu
--- Comment #2 from Theodore Tso <tytso@....edu> 2013-01-21 02:01:26 ---
The file system corruption reported by e2fsck is consistent with the complaint
from the kernel. Specifically, there is an entry in the directory which is
pointing at a deleted inode.
What's not clear is whether this file system corruption is caused by a kernel
bug, or a hardware error (bit flip by the hard drive or the memory), or
something else.
What did you mean by this?
No stack trace (btw I had one two hours before the first EXT4-fs warning
related to RX buffer, see #13561)
What do you mean by see "#13561"?
--
Configure bugmail: https://bugzilla.kernel.org/userprefs.cgi?tab=email
------- You are receiving this mail because: -------
You are watching the assignee of the bug.
--
To unsubscribe from this list: send the line "unsubscribe linux-ext4" in
the body of a message to majordomo@...r.kernel.org
More majordomo info at http://vger.kernel.org/majordomo-info.html
Powered by blists - more mailing lists