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: Tue, 25 Mar 2014 10:11:23 +0000 [thread overview]
Message-ID: <bug-40822-13602-FFHvKEfvQV@https.bugzilla.kernel.org/> (raw)
In-Reply-To: <bug-40822-13602@https.bugzilla.kernel.org/>
https://bugzilla.kernel.org/show_bug.cgi?id=40822
Sebastien Koechlin <seb.kernel@koocotte.org> changed:
What |Removed |Added
----------------------------------------------------------------------------
CC| |seb.kernel@koocotte.org
--- Comment #4 from Sebastien Koechlin <seb.kernel@koocotte.org> ---
Sorry, I did not see that I had an answer on bugzilla. I will monitor it from
now.
Here is the situation:
- The problem came back every few month during this time. I run many fsck, it
usually correct things, but maybe not this particular deleted inode problem
(fsck bug?).
- I updated on 2014-02-10 to kernel 3.13.2 and e2fsck.static to 1.42.9-3
(e2fsck-static_1.42.9-2_i386.deb), and the problem happened today.
- About hardware error: this server is running continuously since this initial
bug report without problem (no other filesystem corrupted, no segfaults, no
kernel ooops...)
- About Host: Debian Linux 32bits, kernel is 64bits, RAID1+LVM2, many-many
hardlinks (an inode has 29542 links), filesystem resized (to grow it) may
times. It's always between 85 and 95% full.
I have in dmesg:
[3654666.866636] EXT4-fs error (device dm-4): ext4_lookup:1437: inode #300243:
comm rsync: deleted inode referenced: 2748375
[3654666.911302] Aborting journal on device dm-4-8.
[3654666.970296] EXT4-fs (dm-4): Remounting filesystem read-only
[3654667.104392] EXT4-fs error (device dm-4): ext4_lookup:1437: inode #300243:
comm rsync: deleted inode referenced: 2748375
Previous was using kernel 3.12.6:
[ 3226.048137] EXT4-fs (dm-4): mounted filesystem with ordered data mode. Opts:
errors=remount-ro,user_xattr
[ 3526.870020] EXT4-fs (dm-4): error count: 21
[ 3526.870108] EXT4-fs (dm-4): initial error at 1372893876: ext4_lookup:1428:
inode 915940
[ 3526.870271] EXT4-fs (dm-4): last error at 1372930167: ext4_put_super:762:
inode 1676891
e2fsck just recover the journal and with -f does not find anything wrong.
--
You are receiving this mail because:
You are watching the assignee of the bug.
next prev parent reply other threads:[~2014-03-25 10:11 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 [this message]
2014-04-11 9:08 ` bugzilla-daemon
2014-04-11 12:33 ` bugzilla-daemon
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-FFHvKEfvQV@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).