From: Chris Mason <chris.mason@oracle.com>
To: Chris Baines <cbaines8@gmail.com>
Cc: linux-btrfs@vger.kernel.org
Subject: Re: bad tree block problems
Date: Tue, 20 Dec 2011 18:36:37 -0500 [thread overview]
Message-ID: <20111220233637.GP19266@shiny> (raw)
In-Reply-To: <CAGGGvRtNCvt9LYvZE1ZEE9tYCS95KLTUdKKXnqDzm8vHbO-vfg@mail.gmail.com>
On Tue, Dec 20, 2011 at 10:34:20PM +0000, Chris Baines wrote:
> Hello,
>
> I am having problems with my btrfs filesystem, I have a 1TB RAID-1
> setup that I use as /home. When accessing certain programs, or moving
> large amounts of data, I often get errors looking like the one
> attached, after I get the error, /home becomes unusable and I reboot.
> I have tried running scrub, but it aborts (output given in the
> attachment).
>
> I am using the 3.2.0-rc4 kernel (as distributed in Debian) at the
> moment, but this may not have been the kernel I was using when I first
> started getting the errors.
It looks like you have both virtual box and nvidia loaded here, so it is
hard to tell exactly where this problem came from.
Could you please grab the latest btrfs-progs and do a:
btrfs inspect logical 714427781120 /home
This will tell us a little more about the bad block.
-chris
next prev parent reply other threads:[~2011-12-20 23:36 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-12-20 22:34 bad tree block problems Chris Baines
2011-12-20 23:36 ` Chris Mason [this message]
2011-12-20 23:39 ` Chris Baines
2011-12-21 1:07 ` Liu Bo
2011-12-21 1:29 ` Chris Baines
[not found] ` <CAGGGvRvVUDbsZKOgqkA+CYfsfpYdHEDF5BYLs3sKVWw+ekH4nQ@mail.gmail.com>
2012-01-18 20:01 ` Chris Baines
2012-01-18 20:48 ` cwillu
2012-01-19 3:26 ` Chris Baines
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=20111220233637.GP19266@shiny \
--to=chris.mason@oracle.com \
--cc=cbaines8@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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.