From: Jan Schmidt <list.btrfs@jan-o-sch.net>
To: Mitch Harder <mitch.harder@sabayonlinux.org>
Cc: linux-btrfs <linux-btrfs@vger.kernel.org>
Subject: Re: NULL Pointer Dereference While Scrubbing
Date: Tue, 17 Jan 2012 18:08:01 +0100 [thread overview]
Message-ID: <4F15AAF1.6090306@jan-o-sch.net> (raw)
In-Reply-To: <CAKcLGm9+TPwngXj0NE0UShreUd=OzUK2_FuXbJTCRA7rzoUOmg@mail.gmail.com>
On 17.01.2012 18:03, Mitch Harder wrote:
> You're correct about my original problem being with scrub. I had lost
> track of the multiple ways to make the partition BUG.
>
> I've re-run scrub, and scrub now proceeds without error also, but it
> still leaves the inode 400 error from btrfsck.
>
> I am beginning to suspect that the partition had another inconsistency
> that didn't have anything to do the the btrfsck reported error, but
> was causing btrfs to run into a BUG when running various operations on
> the disk.
Sounds plausible.
> The current Scrub results are:
>
> # btrfs scrub start -B /mnt/gentoo/
> scrub done for 75b9f12c-7f3a-4bb2-abe4-dc3da29558ed
> scrub started at Tue Jan 17 10:52:26 2012 and finished after 57 seconds
> total bytes scrubbed: 2.91GB with 0 errors
>
> Which still leaves the following btrfsck result:
>
> # btrfsck /dev/sdb5
> root 5 inode 19772 errors 400
> found 3125092352 bytes used err is 1
> total csum bytes: 2476744
> total tree bytes: 588513280
> total fs tree bytes: 554622976
> btree space waste bytes: 146782986
> file data blocks allocated: 2536579072
> referenced 5144166400
> Btrfs Btrfs v0.19-dirty
Alright, that's fine. Scrub isn't expected to find those.
(I_ERR_FILE_NBYTES_WRONG)
-Jan
prev parent reply other threads:[~2012-01-17 17:08 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-01-03 17:35 NULL Pointer Dereference While Scrubbing Mitch Harder
2012-01-17 0:10 ` Mitch Harder
2012-01-17 16:35 ` Mitch Harder
2012-01-17 16:41 ` Jan Schmidt
2012-01-17 16:42 ` Jan Schmidt
2012-01-17 17:03 ` Mitch Harder
2012-01-17 17:08 ` Jan Schmidt [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=4F15AAF1.6090306@jan-o-sch.net \
--to=list.btrfs@jan-o-sch.net \
--cc=linux-btrfs@vger.kernel.org \
--cc=mitch.harder@sabayonlinux.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