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: Thu, 05 Jun 2014 14:59:35 +0000 [thread overview]
Message-ID: <bug-40822-13602-gD9eJUuqDF@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
----------------------------------------------------------------------------
Status|NEW |RESOLVED
Resolution|--- |INVALID
--- Comment #7 from Sebastien Koechlin <seb.kernel@koocotte.org> ---
It's a Debian system, it's performing an array-check every month (by echoing
check into relevant /sys/block/$array/md/sync_action) and I have never seen any
error in dmesg.
But I found a strange drive, its SMART attributes were not updated for more
than 6 month (Power_On_Hours in particular).
I changed this drive and I can not reproduce any error. You've probably guessed
right; so I close this bug.
Thanks a lot.
--
You are receiving this mail because:
You are watching the assignee of the bug.
prev parent reply other threads:[~2014-06-05 14:59 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
2014-06-05 14:59 ` bugzilla-daemon [this message]
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-gD9eJUuqDF@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).