From: Daniel J Blueman <daniel@quora.org>
To: Andrea Gelmini <andrea.gelmini@gmail.com>
Cc: Linux BTRFS <linux-btrfs@vger.kernel.org>,
Chris Mason <chris.mason@oracle.com>
Subject: Re: 'bad tree block start' mount failure...
Date: Wed, 21 Mar 2012 18:19:16 +0800 [thread overview]
Message-ID: <CAMVG2suxFWRY7uc0tv-AZ3pmSyzqhG+hXwzfNv8-a_E+P8On1Q@mail.gmail.com> (raw)
In-Reply-To: <CAK-xaQbAq85UFa41h-As3yDXvVz5ybtGU-ySVYJmcRLc0GgbgA@mail.gmail.com>
On 21 March 2012 00:16, Andrea Gelmini <andrea.gelmini@gmail.com> wrote:
> 2012/3/20 Daniel J Blueman <daniel@quora.org>:
>> mkfs.btrfs -m raid0 -d raid0 /dev/sdb1 /dev/sdc1
>> mount /dev/sdb1 /mnt
>> umount /mnt
>> mount /dev/sdb1 /mnt -o compress
>> umount /mnt
>> mount /dev/sdb1 /mnt -o ssd
>> umount /mnt
>> mount /dev/sdb1 /mnt -o discard
>> umount /mnt
>> mount /dev/sdb1 /mnt
>> <mount failure>
>
> Well, I can't reproduce this. It's also true that I use some
> out-of-the-tree patches.
> I wrote this each step. They must be in a script?
I can reproduce this booting with the ubuntu 3.3 mainline kernel with
eg 'ramdisk_size=2048000' and then:
# mkfs.btrfs -m raid0 -d raid0 /dev/ram0 /dev/ram1
# mount /dev/ram0 /mnt
# umount /mnt
# mount /dev/ram0 /mnt -o compress
# umount /mnt
# mount /dev/ram0 /mnt -o ssd
# umount /mnt
# mount /dev/ram0 /mnt -o discard
# umount /mnt
# mount /dev/ram0 /mnt
mount: wrong fs type, bad option, bad superblock on /dev/ram0,
missing codepage or helper program, or other error
In some cases useful info is found in syslog - try
dmesg | tail or so
Thanks,
Daniel
--
Daniel J Blueman
prev parent reply other threads:[~2012-03-21 10:19 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-03-20 15:43 'bad tree block start' mount failure Daniel J Blueman
2012-03-20 16:16 ` Andrea Gelmini
2012-03-21 10:19 ` Daniel J Blueman [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=CAMVG2suxFWRY7uc0tv-AZ3pmSyzqhG+hXwzfNv8-a_E+P8On1Q@mail.gmail.com \
--to=daniel@quora.org \
--cc=andrea.gelmini@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;
as well as URLs for NNTP newsgroup(s).