Linux Btrfs filesystem development
 help / color / mirror / Atom feed
From: Leszek Ciesielski <skolima@gmail.com>
To: TARUISI Hiroaki <taruishi.hiroak@jp.fujitsu.com>,
	lists-receive <lists-receive@programmierforen.de>,
	jowens <jowens@hp.com>, linux-btrfs <linux-btrfs@vger.kernel.org>
Subject: Re: Unable to mount loopback devices in RAID mode
Date: Tue, 1 Dec 2009 11:27:26 +0100	[thread overview]
Message-ID: <23a15590912010227v38b62a51r63e5d83fdd9fec4c@mail.gmail.com> (raw)
In-Reply-To: <4B14B022.4080102@jp.fujitsu.com>

On Tue, Dec 1, 2009 at 6:56 AM, TARUISI Hiroaki
<taruishi.hiroak@jp.fujitsu.com> wrote:
> Btrfs collects block device information when mount or mkfs
> (device_list_add in volumes.c), and know devid-device relation
> by collected information. So, if we make filesystem on plain
> file, btrfs cannot know devid-device relation. As a result,
> btrfs cannot know which is 'devid=3Dn', and mount fails. Same as
> this, if collected relation is cleared by shutdown, mount fails.
>
> If we need to mount a filesystem without fail(cf, /etc/fstab line),
> we should specify 'device' options for every devices(except mount
> target device) like this.
>
> # mount -t btrfs -o device=3D/dev/loop2,device=3D/dev/loop3,
> =A0device=3D/dev/loop4 /dev/loop1 /mnt/
> =A0 (when a filesystem is constructed by /dev/loop[1-4])
>
> Regards,
> taruisi

Would this option ["mount -t btrfs -o device=3D/dev/sdb2 /dev/sda2
/mnt"] work on boot, bypasing the need for "btrfsctl -a" to mount a
multi-device filesystem?
--
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

  reply	other threads:[~2009-12-01 10:27 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
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 [this message]
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=23a15590912010227v38b62a51r63e5d83fdd9fec4c@mail.gmail.com \
    --to=skolima@gmail.com \
    --cc=jowens@hp.com \
    --cc=linux-btrfs@vger.kernel.org \
    --cc=lists-receive@programmierforen.de \
    --cc=taruishi.hiroak@jp.fujitsu.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