From: Sjoerd <sjoerd@sjomar.eu>
To: linux-btrfs@vger.kernel.org
Subject: Re: RAID5 doesn't mount on boot, but you can afterwards?
Date: Thu, 01 Oct 2015 19:04:43 +0200 [thread overview]
Message-ID: <1787237.MVYq6GNlXh@hoefnix> (raw)
In-Reply-To: <pan$b6f45$856590$f682594c$bd5aae60@cox.net>
On Thursday 01 October 2015 02:21:23 Duncan wrote:
> That's very likely because unlike traditional single-device filesystems
> (including single-device btrfs), multi-device btrfs has multiple devices
> it must know about before it can mount the device, while mount only feeds
> it one device.
>
> There are two ways to tell btrfs (the kernel side) about the other
> devices.
>
> 1) Do a btrfs device scan before trying to mount.
>
> 2) Name the component devices in the mount options, using the device=
> option (multiple times as necessary to list all devices).
>
Option 2 was to simplest to check and that works. Thanks for the tip!
Still weird that my single devide SSD BTRFS bootdisk just worked fine
(althought it's using the uuid offcourse)...But it would imply to me that
there's a btrfs device scan run before mounting it.
Before I created the RAID5 I just had the four disks configures as JBOD in
btrfs (I used partitions that time though) and mounted it just fine with the
LABEL only, so it might be something with RAID5.
Anyway it's working now with just a much longer fstab line ;)
Cheers,
Sjoerd
next prev parent reply other threads:[~2015-10-01 17:04 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-09-30 16:49 RAID5 doesn't mount on boot, but you can afterwards? Sjoerd
2015-09-30 19:04 ` Leonidas Spyropoulos
[not found] ` <1501fba4ad0.2767.ff8c1290f37e89588b661f56613851bb@sjomar.eu>
2015-09-30 19:29 ` Sjoerd
2015-10-01 2:21 ` Duncan
2015-10-01 17:04 ` Sjoerd [this message]
2015-10-01 17:46 ` Hugo Mills
2015-10-02 1:11 ` Duncan
2015-10-03 20:53 ` guido_kuenne
2015-10-04 2:28 ` Duncan
2015-10-04 11:51 ` Sjoerd
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=1787237.MVYq6GNlXh@hoefnix \
--to=sjoerd@sjomar.eu \
--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).