From: Liu Bo <liubo2009@cn.fujitsu.com>
To: Chris Baines <cbaines8@gmail.com>
Cc: Chris Mason <chris.mason@oracle.com>, linux-btrfs@vger.kernel.org
Subject: Re: bad tree block problems
Date: Wed, 21 Dec 2011 09:07:34 +0800 [thread overview]
Message-ID: <4EF13156.302@cn.fujitsu.com> (raw)
In-Reply-To: <CAGGGvRucivqjTz4X7LNdTo_Nx_oXY9wOor4f7zbnbCf_+-XKPw@mail.gmail.com>
On 12/21/2011 07:39 AM, Chris Baines wrote:
> On 20 December 2011 23:36, Chris Mason <chris.mason@oracle.com> wrote:
>> 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
>>
>
> How do I do this exactly, do I build a kernel from git?
>
Only building the btrfs-progs will be ok.
To get btrfs-progs:
git://git.kernel.org/pub/scm/linux/kernel/git/mason/btrfs-progs.git
thanks,
liubo
> Thanks,
>
> Chris
> --
> 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:[~2011-12-21 1:07 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
2011-12-20 23:39 ` Chris Baines
2011-12-21 1:07 ` Liu Bo [this message]
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=4EF13156.302@cn.fujitsu.com \
--to=liubo2009@cn.fujitsu.com \
--cc=cbaines8@gmail.com \
--cc=chris.mason@oracle.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