From: Chris Mason <chris.mason@oracle.com>
To: Johannes Hirte <johannes.hirte@fem.tu-ilmenau.de>
Cc: John Dong <jdong@ubuntu.com>, linux-btrfs@vger.kernel.org
Subject: Re: btrfsck aborts after transid verify failed?
Date: Mon, 2 Nov 2009 16:44:05 -0500 [thread overview]
Message-ID: <20091102214405.GF4560@think> (raw)
In-Reply-To: <200910272323.43797.johannes.hirte@fem.tu-ilmenau.de>
On Tue, Oct 27, 2009 at 11:23:43PM +0100, Johannes Hirte wrote:
> Am Montag 26 Oktober 2009 10:41:04 schrieb Chris Mason:
> > > On 10/21/2009 09:44 AM, Yan, Zheng wrote:
> > > >On Wed, Oct 21, 2009 at 9:21 PM, John Dong<jdong@ubuntu.com> wrote:
> > > >>> On Oct 21, 2009, at 3:47 AM, Yan, Zheng wrote:
> > > >>>>> Did you run btrfsck on mounted FS ?
> > > >>>>>
> > > >>>>> Yan, Zheng
> > > >>>
> > > >>> Yes, I did. I thought it was okay to do so?
> > > >
> > > >No, btrfs doesn't support that.
> > >
> > > Whoops! My bad then!
> > >
> > > BTW, the wiki still says
> > >
> > > http://btrfs.wiki.kernel.org/index.php/Btrfsck:
> > >
> > > Do a limited check of the FS extent trees. Can be run on mounted and
> > > unmounted FS.
> >
> > Thanks!, I've updated the docs.
>
> Will this be added in future or is this feature completely thrown away?
It is definitely on the list to be added in the future. Online fsck is
a big part of my plans for keeping btrfs usable in the long term.
-chris
next prev parent reply other threads:[~2009-11-02 21:44 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-10-21 13:48 btrfsck aborts after transid verify failed? John Dong
2009-10-26 9:41 ` Chris Mason
2009-10-27 22:23 ` Johannes Hirte
2009-11-02 21:44 ` Chris Mason [this message]
-- strict thread matches above, loose matches on Subject: below --
2009-10-21 6:05 John Dong
2009-10-21 7:47 ` Yan, Zheng
2009-10-21 13:21 ` John Dong
2009-10-21 13:44 ` Yan, Zheng
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=20091102214405.GF4560@think \
--to=chris.mason@oracle.com \
--cc=jdong@ubuntu.com \
--cc=johannes.hirte@fem.tu-ilmenau.de \
--cc=linux-btrfs@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