From: Roman Mamedov <rm@romanrm.ru>
To: "Richard W.M. Jones" <rjones@redhat.com>
Cc: linux-btrfs@vger.kernel.org
Subject: Re: What can I do to make btrfs work?
Date: Wed, 13 Feb 2013 02:08:50 +0600 [thread overview]
Message-ID: <20130213020850.77d5aca4@natsu> (raw)
In-Reply-To: <20130212185449.GA16773@rhmail.home.annexia.org>
[-- Attachment #1: Type: text/plain, Size: 1876 bytes --]
On Tue, 12 Feb 2013 18:54:49 +0000
"Richard W.M. Jones" <rjones@redhat.com> 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!
I might be pointing out the most obvious here, but where does /dev/sda2 come
from?
Some more ideas for you to try
dd if=/dev/zero of=/dev/sda bs=1M count=1
blockdev --rereadpt /dev/sda
and then proceed again with your test loop.
> ----------------------------------------------------------------------
> #!/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
^^^^^^^^^^^^^^^^^^^^^^ sda1
> 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
^^^^ 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?
>
> Rich.
>
> [1] http://article.gmane.org/gmane.comp.file-systems.btrfs/20257
>
--
With respect,
Roman
[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 198 bytes --]
prev parent reply other threads:[~2013-02-12 20:08 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
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 [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=20130213020850.77d5aca4@natsu \
--to=rm@romanrm.ru \
--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