From: jim owens <jowens@hp.com>
To: Andi Drebes <lists-receive@programmierforen.de>
Cc: linux-btrfs@vger.kernel.org
Subject: Re: Unable to mount loopback devices in RAID mode
Date: Thu, 19 Nov 2009 18:35:39 -0500 [thread overview]
Message-ID: <4B05D64B.7070705@hp.com> (raw)
In-Reply-To: <200911192026.04694.lists-receive@programmierforen.de>
Andi Drebes wrote:
> Hi!
> I recently tried to mount a filesystem in RAID1 mode using loopback devices. I followed the instructions at [1]. Here's exactly what I've done:
>
> $ dd if=/dev/zero of=raid1_0.img bs=1M count=500
> $ dd if=/dev/zero of=raid1_1.img bs=1M count=500
> $ mkfs.btrfs -m raid1 -d raid1 raid1_0.img raid1_1.img
> $ losetup /dev/loop0 raid1_0.img
> $ losetup /dev/loop1 raid1_1.img
> $ mount -t btrfs /dev/loop0 /mnt/btrfs
> mount: wrong fs type, bad option, bad superblock on /dev/loop0,
> missing codepage or helper program, or other error
> In some cases useful info is found in syslog - try
> dmesg | tail or so
The problem is btrfs randomly changes the "current master"
superblock of the filesystem. Only 1 of the devices will
be mountable. You just have to try the other ones, like:
> $ mount -t btrfs /dev/loop0 /mnt/btrfs
> mount: wrong fs type, bad option, bad superblock on /dev/loop0,
$ mount -t btrfs /dev/loop1 /mnt/btrfs
until you find one that works. I've been testing 4 devices
and often have to try all 4. Maybe someday we will fix this
so ANY raid member can start the mount (but this may need
a disk format change).
jim
next prev parent reply other threads:[~2009-11-19 23:35 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-11-19 19:26 Unable to mount loopback devices in RAID mode Andi Drebes
2009-11-19 23:35 ` jim owens [this message]
2009-11-20 19:22 ` Andi Drebes
2009-11-27 5:33 ` Jean-Sébastien Trottier
2009-11-27 15:57 ` jim owens
2009-11-30 4:28 ` Jean-Sébastien Trottier
2009-11-30 13:09 ` jim owens
2009-11-30 19:25 ` Andi Drebes
2009-12-01 5:56 ` TARUISI Hiroaki
2009-12-01 10:27 ` Leszek Ciesielski
2009-12-01 23:52 ` TARUISI Hiroaki
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=4B05D64B.7070705@hp.com \
--to=jowens@hp.com \
--cc=linux-btrfs@vger.kernel.org \
--cc=lists-receive@programmierforen.de \
/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.