From: Theodore Ts'o <tytso@mit.edu>
To: Akos Csete <akos.csete@gmail.com>
Cc: "Darrick J. Wong" <darrick.wong@oracle.com>, linux-ext4@vger.kernel.org
Subject: Re: Fsck repair takes very long for 1,761 inodes containing multiply-claimed blocks on ext4
Date: Fri, 17 Apr 2015 17:08:51 -0400 [thread overview]
Message-ID: <20150417210851.GB9700@thunk.org> (raw)
In-Reply-To: <CAD-ux61ti+D7_O2Xrtap5WEi7aFryQ4JoX4eO+J7dcuJS=DZag@mail.gmail.com>
On Fri, Apr 17, 2015 at 04:05:04PM -0400, Akos Csete wrote:
>
> Could I then just wipe the inodes of the older files (and restore them
> later from backup) and let the new file claim those blocks? Or are the
> new file's claim to those blocks suspect?
OK, if the mod times are different, then it probably wasn't a case of
an inode getting written to the wrong place on disk. What probably
did happen is the block allocation bitmaps got corrupted, and so
blocks that were in use (and should have been marked in use) were not,
so they got used for some other inode.
So yes, you can try wiping the inodes for the older files, and hope
for the best, but it may be that some of the newer files may end up
getting corrupted. So you might want to do some spot checks
afterwards. And if you have backups, this might be a good time to
consider going to your backup tapes....
- Ted
next prev parent reply other threads:[~2015-04-17 21:09 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-04-15 15:18 Fsck repair takes very long for 1,761 inodes containing multiply-claimed blocks on ext4 Akos Csete
2015-04-15 19:06 ` Darrick J. Wong
2015-04-16 15:00 ` Theodore Ts'o
2015-04-17 20:05 ` Akos Csete
2015-04-17 21:08 ` Theodore Ts'o [this message]
2015-04-18 15:02 ` Andreas Dilger
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=20150417210851.GB9700@thunk.org \
--to=tytso@mit.edu \
--cc=akos.csete@gmail.com \
--cc=darrick.wong@oracle.com \
--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).