From: Eric Sandeen <sandeen@redhat.com>
To: Andreas Dilger <adilger.kernel@dilger.ca>
Cc: Lukas Czerner <lczerner@redhat.com>,
Ric Wheeler <ricwheeler@gmail.com>,
linux-ext4@vger.kernel.org, tytso@mit.edu
Subject: Re: [PATCH] e2fsck: Discard free data and inode blocks.
Date: Fri, 22 Oct 2010 13:27:19 -0500 [thread overview]
Message-ID: <4CC1D787.5000707@redhat.com> (raw)
In-Reply-To: <0694FED8-F35E-4D46-9DF9-E60855E2F2B5@dilger.ca>
Andreas Dilger wrote:
> On 2010-10-22, at 08:32, Lukas Czerner wrote:
>>>> There is a concern that discard might prevent data recovery
>>>> after fsck because it might be already discarded (some weird fs
>>>> corruption?) in pass 5. However in my opinion this is a very
>>>> small window (if there even is any), because we have already
>>>> passed check 1-4 and we have just confirmed that group
>>>> descriptors should be ok.
>
> I don't totally agree. When users have a serious filesystem problem,
> the first thing they normally do is run e2fsck to see if it is
> corrected (it may even be done automatically at boot after
> errors=panic causing a reboot.
>
> After that, they may want to recover some more data (e.g. with
> ext3grep, or restore an e2image of the metadata, and re-run e2fsck).
> If e2fsck will discard all of the data then any data recovery will be
> impossible.
Could set it to only issue discard when the check was clean....
It could still be an option of course, but that might be safer still.
-Eric
next prev parent reply other threads:[~2010-10-22 18:27 UTC|newest]
Thread overview: 25+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-10-21 14:15 [PATCH] e2fsck: Discard free data and inode blocks Lukas Czerner
2010-10-21 18:07 ` Andreas Dilger
2010-10-22 9:12 ` Lukas Czerner
2010-10-22 11:30 ` Ric Wheeler
2010-10-22 11:43 ` Lukas Czerner
2010-10-22 14:12 ` Ric Wheeler
2010-10-22 14:32 ` Lukas Czerner
2010-10-22 14:46 ` Ric Wheeler
2010-10-22 15:37 ` Eric Sandeen
2010-10-22 15:41 ` Ric Wheeler
2010-10-22 17:03 ` Martin K. Petersen
2010-10-22 17:14 ` Ric Wheeler
2010-10-22 17:29 ` Martin K. Petersen
2010-10-22 18:23 ` Eric Sandeen
2010-10-22 17:50 ` Andreas Dilger
2010-10-22 18:01 ` Lukas Czerner
2010-10-22 18:17 ` Andreas Dilger
2010-10-22 18:23 ` Ric Wheeler
2010-10-22 21:19 ` Martin K. Petersen
2010-10-22 18:29 ` Eric Sandeen
2010-10-22 21:01 ` Martin K. Petersen
2010-10-22 18:00 ` Andreas Dilger
2010-10-22 18:27 ` Eric Sandeen [this message]
2010-10-22 18:31 ` Lukas Czerner
-- strict thread matches above, loose matches on Subject: below --
2010-10-11 10:37 Lukas Czerner
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=4CC1D787.5000707@redhat.com \
--to=sandeen@redhat.com \
--cc=adilger.kernel@dilger.ca \
--cc=lczerner@redhat.com \
--cc=linux-ext4@vger.kernel.org \
--cc=ricwheeler@gmail.com \
--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.