Linux Btrfs filesystem development
 help / color / mirror / Atom feed
From: Chris Mason <chris.mason@fusionio.com>
To: "Richard W.M. Jones" <rjones@redhat.com>
Cc: "linux-btrfs@vger.kernel.org" <linux-btrfs@vger.kernel.org>
Subject: Re: What can I do to make btrfs work?
Date: Tue, 12 Feb 2013 14:02:58 -0500	[thread overview]
Message-ID: <20130212190258.GH16687@shiny.masoncoding.com> (raw)
In-Reply-To: <20130212185449.GA16773@rhmail.home.annexia.org>

On Tue, Feb 12, 2013 at 11:54:49AM -0700, Richard W.M. Jones wrote:
> Btrfs has been broken for me for ages.  I first reported it on this
> list 5 months ago[1].  Below is a very simple reproducer that anyone
> can run.
> 
> *NB* before you run this, adjust /dev/sda & /dev/sda1 to point to an
> unused block device!
> 
> ----------------------------------------------------------------------
> #!/bin/sh -
> set -e
> while true; do
>   parted -s -- /dev/sda mklabel msdos
>   parted -s -- /dev/sda mkpart primary 64s -64s
>   wipefs -a /dev/sda1
>   mkfs.btrfs --label TEST /dev/sda1
>   mount /dev/sda1 /sysroot
>   touch /sysroot/foo
>   mkdir /sysroot/bar
>   umount /sysroot
> done
> ----------------------------------------------------------------------
> 
> On the latest 3.8.0 kernel, this fails immediately (at the mount), and
> on 3.7.x it usually fails after a very few iterations.  I see a
> variety of errors, but the latest kernel error is:
> 
> [    8.474934] device label ROOT devid 1 transid 2 /dev/sda2
> [    8.570619] device label ROOT devid 1 transid 2 /dev/sda2
> [    8.581891] btrfs: disk space caching is enabled
> [    8.594146] btrfs bad tree block start 0 4194304
> [    8.595144] btrfs: failed to read tree root on sda2
> [    8.605308] btrfs: open_ctree failed
> 
> I would really like btrfs to work.  What can I do?

Hi Rich,

Can you try the btrfs-progs raid56-experimental branch.  It has this
patch which was fixing things for me:

https://git.kernel.org/?p=linux/kernel/git/mason/btrfs-progs.git;a=commit;h=8fe354744cd7b5c4f7a3314dcdbb5095192a032f

I'm not 100% sure I've reproduced your exact problem, but I hope this is
it.

-chris

  reply	other threads:[~2013-02-12 19:03 UTC|newest]

Thread overview: 12+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2013-02-12 18:54 What can I do to make btrfs work? Richard W.M. Jones
2013-02-12 19:02 ` Chris Mason [this message]
2013-02-12 19:16 ` Josef Bacik
2013-02-12 21:05   ` Richard W.M. Jones
2013-02-12 21:42     ` Chris Mason
2013-02-13 11:00       ` Richard W.M. Jones
2013-02-13 13:10         ` Richard W.M. Jones
2013-02-13 13:31           ` Chris Mason
2013-02-15 18:38             ` Chris Mason
2013-02-12 19:44 ` Zach Brown
2013-02-12 21:06   ` Richard W.M. Jones
2013-02-12 20:08 ` Roman Mamedov

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=20130212190258.GH16687@shiny.masoncoding.com \
    --to=chris.mason@fusionio.com \
    --cc=linux-btrfs@vger.kernel.org \
    --cc=rjones@redhat.com \
    /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