From: Josef Bacik <josef@redhat.com>
To: Adrian von Bidder <avbidder@fortytwo.ch>
Cc: linux-btrfs@vger.kernel.org
Subject: Re: btrfsck: doesn't correct errors
Date: Thu, 27 May 2010 14:15:53 -0400 [thread overview]
Message-ID: <20100527181553.GF25333@dhcp231-156.rdu.redhat.com> (raw)
In-Reply-To: <201005271846.16832@fortytwo.ch>
On Thu, May 27, 2010 at 06:46:04PM +0200, Adrian von Bidder wrote:
> Heyho!
>
> (This is using btrfs from Debian's 2.6.32 2.6.32-3-kirkwood kernel (-9
> package; btrfs tools is v0.19-16-g075587c)
>
> A few observations about btrfsck:
>
> a btrfsck run on a 2T volume (4 disks) on a QNAP appliance (512M ram) got
> killed by Mr. OOM Killer. Initially, I was quite surprised. I'm only
> moderately surprised now since it might well be that I forgot to enable
> swap.
>
Yes, btrfsck keeps the entire extent tree in memory, so the bigger the fs, the
more RAM it's going to use.
> A btrfsck run (on a remote machine this time, with nbd) showed quite a few
> errors like:
> root 268 inode 34001 errors 2000
> root 268 inode 34002 errors 2000
> root 268 inode 34074 errors 2000
> root 268 inode 34102 errors 2000
> root 268 inode 34103 errors 2000
> root 268 inode 34104 errors 2000
> root 268 inode 34132 errors 2000
> root 268 inode 34133 errors 2000
>
> 2nd observation: am I supposed to know what this means?
>
No not really, atm it's just for us developers.
> And 3rd observation: btrfsck apparently doesn't correct this kind of error.
> Running btrfsck again still shows the error.
>
Yeah btrfsck doesn't fix problems yet. Thats being worked on. Thanks,
Josef
next prev parent reply other threads:[~2010-05-27 18:15 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-05-27 16:46 btrfsck: doesn't correct errors Adrian von Bidder
2010-05-27 18:15 ` Josef Bacik [this message]
2010-05-27 20:02 ` Adrian von Bidder
2010-05-28 1:57 ` Trent W. Buck
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=20100527181553.GF25333@dhcp231-156.rdu.redhat.com \
--to=josef@redhat.com \
--cc=avbidder@fortytwo.ch \
--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).