From: Chris Mason <chris.mason@oracle.com>
To: Andi Kleen <andi@firstfloor.org>
Cc: Hubert Kario <hka@qbs.com.pl>, Li Zefan <lizf@cn.fujitsu.com>,
Btrfs mailing list <linux-btrfs@vger.kernel.org>
Subject: Re: [PATCH] Btrfs: initial online fsck support
Date: Wed, 20 Jul 2011 11:06:51 -0400 [thread overview]
Message-ID: <1311174334-sup-9998@shiny> (raw)
In-Reply-To: <20110702170443.GI23059@one.firstfloor.org>
Excerpts from Andi Kleen's message of 2011-07-02 13:04:43 -0400:
> > The two big features of btrfs are self-healing and online fsck, those have to
>
> Are they?
>
> > be implemented in kernel space.
>
> Why? There have been online fscks in user space in the past,
> e.g. the various schemes using LVM snapshots for ext* and
> other related work on the BSD FFS. I don't see any principal
> reason why it couldn't be done for btrfs either.
>
> A good fsck is quite complex and you are unlikely to want all
> that code in kernel space.
The offline fsck for btrfs is basically for repairing the worst possible
problems (things that make the FS unmountable).
The online code can easily take on smaller things, like detecting
incorrect link counts and a whole series of other problems that
shouldn't require offline access.
-chris
prev parent reply other threads:[~2011-07-20 15:06 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-06-30 9:33 [PATCH] Btrfs: initial online fsck support Li Zefan
2011-07-01 17:48 ` Andi Kleen
2011-07-02 11:47 ` Hubert Kario
2011-07-02 17:04 ` Andi Kleen
2011-07-02 19:06 ` Hubert Kario
2011-07-20 15:06 ` Chris Mason [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=1311174334-sup-9998@shiny \
--to=chris.mason@oracle.com \
--cc=andi@firstfloor.org \
--cc=hka@qbs.com.pl \
--cc=linux-btrfs@vger.kernel.org \
--cc=lizf@cn.fujitsu.com \
/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).