From: Zlatko Calusic <zcalusic@bitsync.net>
To: linux-ext4@vger.kernel.org
Subject: e2fsck not fixing deleted inode referenced errors?
Date: Tue, 30 Sep 2014 19:56:36 +0200 [thread overview]
Message-ID: <542AEED4.5050303@bitsync.net> (raw)
Hope this is the right list to ask this question.
I have an ext4 filesystem that has a few errors like this:
Sep 30 19:14:09 atlas kernel: EXT4-fs error (device md2):
ext4_lookup:1448: inode #7913865: comm find: deleted inode referenced:
7912058
Sep 30 19:14:09 atlas kernel: EXT4-fs error (device md2):
ext4_lookup:1448: inode #7913865: comm find: deleted inode referenced:
7912055
Yet, when I run e2fsck -fy on it, I have a clean run, no errors are
found and/or fixed. Is this the expected behaviour? What am I supposed
to do to get rid of errors like the above?
The filesystem is on a md mirror device, the kernel is 3.17.0-rc7,
e2progs 1.42.12-1 (Debian sid). Could md device somehow interfere? I ran
md check yesterday, but there were no errors.
BTW, this all started when I got ata2.00: failed command: FLUSH CACHE
EXT error yesterday morning. I did several runs of e2fsck before the
filesystem came up clean, yet errors like the above are popping constantly.
Thanks for any info. [and please Cc:, I'm not subscribed]
--
Zlatko
next reply other threads:[~2014-09-30 18:05 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-09-30 17:56 Zlatko Calusic [this message]
2014-09-30 18:30 ` e2fsck not fixing deleted inode referenced errors? Darrick J. Wong
2014-09-30 18:43 ` Zlatko Calusic
2014-09-30 19:29 ` Darrick J. Wong
2014-09-30 20:10 ` Zlatko Calusic
2014-09-30 19:54 ` Theodore Ts'o
2014-09-30 20:27 ` Zlatko Calusic
2014-09-30 20:36 ` Darrick J. Wong
2014-09-30 21:34 ` Zlatko Calusic
2014-10-01 6:44 ` Zlatko Calusic
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=542AEED4.5050303@bitsync.net \
--to=zcalusic@bitsync.net \
--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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.