From: Zlatko Calusic <zcalusic@bitsync.net>
To: Theodore Ts'o <tytso@mit.edu>
Cc: "Darrick J. Wong" <darrick.wong@oracle.com>, linux-ext4@vger.kernel.org
Subject: Re: e2fsck not fixing deleted inode referenced errors?
Date: Wed, 01 Oct 2014 08:44:00 +0200 [thread overview]
Message-ID: <542BA2B0.4040604@bitsync.net> (raw)
In-Reply-To: <542B1220.8020208@bitsync.net>
On 30.09.2014 22:27, Zlatko Calusic wrote:
>
> Unless you have other ideas, I will run badblocks. Although, as ext4 fs
> is on /dev/md2, I think I should run it on /dev/md2 only? Do you really
> mean to run it on /dev/sda2, /dev/sdb2 - underlying devices? I'm not
> sure how MD would cope with it.
>
> But, I'm pretty sure that it will come out clean. The md check I did
> last night would surely detected bad blocks if there were any. Or not?
So, I ran badblocks on both underlying devices, and both came up clean,
as I suspected would happen. Then I ran debugfs -w /dev/md2 and unlinked
7 inodes that were problematic. Afterwards e2fsck found those inodes and
connected them to lost+found. Second e2fsck run finished clean. And at
this time I see no errors on the fs.
This is definitely the case where e2fsck can't see or repair fs errors
that are real.
Regards,
--
Zlatko
prev parent reply other threads:[~2014-10-01 6:44 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-09-30 17:56 e2fsck not fixing deleted inode referenced errors? Zlatko Calusic
2014-09-30 18:30 ` 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 [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=542BA2B0.4040604@bitsync.net \
--to=zcalusic@bitsync.net \
--cc=darrick.wong@oracle.com \
--cc=linux-ext4@vger.kernel.org \
--cc=tytso@mit.edu \
/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.