From: bugzilla-daemon@bugzilla.kernel.org
To: linux-ext4@vger.kernel.org
Subject: [Bug 40822] EXT4-fs error (device dm-4): ext4_lookup:1044: inode #3308277: comm rm: deleted inode referenced: 3058008
Date: Fri, 11 Apr 2014 12:33:49 +0000 [thread overview]
Message-ID: <bug-40822-13602-8Dm06dSrQg@https.bugzilla.kernel.org/> (raw)
In-Reply-To: <bug-40822-13602@https.bugzilla.kernel.org/>
https://bugzilla.kernel.org/show_bug.cgi?id=40822
--- Comment #6 from Theodore Tso <tytso@mit.edu> ---
The fact that the first fsck had just summary accounting errors in pass 1, and
then a subsequent, back-to-back fsck showed errors in pass2, screams either (a)
some kind of hardware error, (b) the two mirrored copies of the RAID1 are out
of sync, or (c) someone or something else was modifying the filesytem at the
same time (i.e., the file system was mounted, and for some reason e2fsck's
safety checks didn't trigger, or it some other fsck or userspace program was
running at the same time, etc.)
I'm going to guess that (b) is the most likely, since this is a local
filesystem (i.e., you're not using fibre channel, or a remote block device, or
a dual-hosted SCSI arrangement or anything else exotic). Could you try to
force a resync of the RAID mirrors, and then run another e2fsck -f check?
--
You are receiving this mail because:
You are watching the assignee of the bug.
next prev parent reply other threads:[~2014-04-11 12:33 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-08-10 8:57 [Bug 40822] New: EXT4-fs error (device dm-4): ext4_lookup:1044: inode #3308277: comm rm: deleted inode referenced: 3058008 bugzilla-daemon
2013-01-20 20:32 ` [Bug 40822] " bugzilla-daemon
2013-01-21 2:01 ` bugzilla-daemon
2013-09-06 7:35 ` bugzilla-daemon
2013-12-23 14:15 ` bugzilla-daemon
2014-03-25 10:11 ` bugzilla-daemon
2014-04-11 9:08 ` bugzilla-daemon
2014-04-11 12:33 ` bugzilla-daemon [this message]
2014-06-05 14:59 ` bugzilla-daemon
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=bug-40822-13602-8Dm06dSrQg@https.bugzilla.kernel.org/ \
--to=bugzilla-daemon@bugzilla.kernel.org \
--cc=linux-ext4@vger.kernel.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).