From: Sean Bartell <wingedtachikoma@gmail.com>
To: ulmo@sonic.net
Cc: linux-btrfs@vger.kernel.org
Subject: Re: Is there a more aggressive fixer than btrfsck?
Date: Wed, 2 Jun 2010 11:56:46 -0400 [thread overview]
Message-ID: <20100602155646.GA4041@flcl.lan> (raw)
In-Reply-To: <a51eea046c4dd444f9d90742beb41a6a.squirrel@webmail.sonic.net>
On Tue, Jun 01, 2010 at 07:29:56PM -0700, ulmo@sonic.net wrote:
> Is there a more aggressive filesystem restorer than btrfsck? It simply
> gives up immediately with the following error:
>
> btrfsck: disk-io.c:739: open_ctree_fd: Assertion `!(!tree_root->node)'
> failed.
btrfsck currently only checks whether a filesystem is consistent. It
doesn't try to perform any recovery or error correction at all, so it's
mostly useful to developers. Any error handling occurs while the
filesystem is mounted.
> Yet, the filesystem has plenty of data on it, and the discs are good and I
> didn't do anything to the data except regular btrfs commands and normal
> mounting. That's a wildly unreliable filesystem.
btrfs is under heavy development, so make sure you're using the latest
git versions of the kernel module and tools.
> BTW, is there a way to improve delete and copy performance of btrfs? I'm
> getting about 50KB/s-500KB/s (per size of file being deleted) in deleting
> and/or copying files on a disc that usually can go about 80MB/s. I think
> it's because they were fragmented. That implies btrfs is too accepting of
> writing data in fragmented style when it doesn't have to. Almost all the
> files on my btrfs partitions are around a gig, or 20 gigs, or a third of a
> gig, or stuff like that. The filesystem is 1.1TB.
>
> Brad
next prev parent reply other threads:[~2010-06-02 15:56 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 [this message]
2010-06-28 13:48 ` Daniel Kozlowski
2010-06-29 2:31 ` Rodrigo E. De León Plicet
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=20100602155646.GA4041@flcl.lan \
--to=wingedtachikoma@gmail.com \
--cc=linux-btrfs@vger.kernel.org \
--cc=ulmo@sonic.net \
/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).