From: "Rodrigo E. De León Plicet" <rdeleonp@gmail.com>
To: Daniel Kozlowski <dan.kozlowski@gmail.com>
Cc: linux-btrfs@vger.kernel.org
Subject: Re: Is there a more aggressive fixer than btrfsck?
Date: Mon, 28 Jun 2010 21:31:49 -0500 [thread overview]
Message-ID: <AANLkTilC9MjM7RK3b-8owdiRJUYnfmc0dIM5nt9Texla@mail.gmail.com> (raw)
In-Reply-To: <loom.20100628T154422-48@post.gmane.org>
On Mon, Jun 28, 2010 at 8:48 AM, Daniel Kozlowski
<dan.kozlowski@gmail.com> wrote:
> Sean Bartell <wingedtachikoma <at> gmail.com> writes:
>
>> > Is there a more aggressive filesystem restorer than btrfsck? =C2=A0=
It simply
>> > gives up immediately with the following error:
>> >
>> > btrfsck: disk-io.c:739: open_ctree_fd: Assertion `!(!tree_root->no=
de)'
>> > failed.
>>
>> btrfsck currently only checks whether a filesystem is consistent. It
>> doesn't try to perform any recovery or error correction at all, so i=
t's
>> mostly useful to developers. Any error handling occurs while the
>> filesystem is mounted.
>>
>
> Is there any plan to implement this functionality. It would seem to m=
e to be a
> pretty basic feature that is missing ?
If Btrfs aims to be at least half of what ZFS is, then it will not
impose a need for fsck at all.
Read "No, ZFS really doesn't need a fsck" at the following URL:
http://www.c0t0d0s0.org/archives/6071-No,-ZFS-really-doesnt-need-a-fsck=
=2Ehtml
--
To unsubscribe from this list: send the line "unsubscribe linux-btrfs" =
in
the body of a message to majordomo@vger.kernel.org
More majordomo info at http://vger.kernel.org/majordomo-info.html
next prev parent reply other threads:[~2010-06-29 2:31 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-06-02 2:29 Is there a more aggressive fixer than btrfsck? ulmo
2010-06-02 15:56 ` Sean Bartell
2010-06-28 13:48 ` Daniel Kozlowski
2010-06-29 2:31 ` Rodrigo E. De León Plicet [this message]
2010-06-29 10:37 ` Daniel Kozlowski
2010-06-29 16:34 ` Hubert Kario
2010-06-29 23:19 ` Anthony Roberts
2010-06-29 21:36 ` Freddie Cash
2010-06-29 22:22 ` Sean Bartell
2010-06-30 1:32 ` Chris Mason
[not found] ` <87eifov564.fsf@mid.deneb.enyo.de>
2010-07-01 3:38 ` Rodrigo E. De León Plicet
2010-07-01 10:09 ` Chris Mason
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=AANLkTilC9MjM7RK3b-8owdiRJUYnfmc0dIM5nt9Texla@mail.gmail.com \
--to=rdeleonp@gmail.com \
--cc=dan.kozlowski@gmail.com \
--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;
as well as URLs for NNTP newsgroup(s).