From: Saint Germain <saintger@gmail.com>
To: linux-btrfs@vger.kernel.org
Subject: Re: BTRFS with RAID1 cannot boot when removing drive
Date: Wed, 12 Feb 2014 18:16:38 +0100 [thread overview]
Message-ID: <CAJbEPe6+3uH97z-oA-QCb-cCb_xDXb016YLP+gZM1wAdMk2KGw@mail.gmail.com> (raw)
In-Reply-To: <pan$9c91a$c8fe6c36$f85dce0f$d0a92204@cox.net>
On 11 February 2014 21:35, Duncan <1i5t5.duncan@cox.net> wrote:
> Saint Germain posted on Tue, 11 Feb 2014 11:04:57 +0100 as excerpted:
>
>> The big problem I currently have is that based on your input, I hesitate
>> a lot on my partitioning scheme: should I use a dedicated /boot
>> partition or should I have one global BTRFS partition ?
>> It is not very clear in the doc (a lof of people used a dedicated /boot
>> because at that time, grub couldn't natively boot BTRFS it seems, but it
>> has changed).
>> Could you recommend a partitioning scheme for a simple RAID1 with 2
>> identical hard drives (just for home computing, not business).
>
> FWIW... I'm planning to and have your previous message covering that
> still marked unread to reply to later. But "real life" has temporarily
> been monopolizing my time so the last day or two I've only done
> relatively short and quick replies. That one will require a bit more
> time to answer to my satisfaction.
>
> So I'm punting for the moment. But FWIW I tend to be a reasonably heavy
> partitioner (tho nowhere near what I used to be), so a lot of folks will
> consider my setup somewhat extreme. That's OK. It's my computer, setup
> for my purposes, not their computer for theirs, and it works very well
> for me, so it's all good. =:^)
>
> But hopefully I'll get back to that with a longer reply by the end of the
> week. If I don't, you can probably consider that monopoly lasting longer
> than I thought, and it could be that I'll never get back to properly
> reply. But it's an interesting enough topic to me that I'll /probably/
> get back, just not right ATM.
>
No problem, I have started another thread where we discuss partitioning.
It may be slightly off-topic, but the intention is really to have a
partition BTRFS-friendly.
For instance it seems that a dedicated /boot partition instead of a
subvolume is not necessary (better to have the /boot in the RAID1).
However I'm no expert.
Thanks for your help.
next prev parent reply other threads:[~2014-02-12 17:16 UTC|newest]
Thread overview: 16+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-02-09 21:40 BTRFS with RAID1 cannot boot when removing drive Saint Germain
2014-02-10 3:34 ` Duncan
2014-02-11 2:30 ` Saint Germain
2014-02-14 14:33 ` Saint Germain
2014-02-16 15:30 ` Saint Germain
2014-02-11 2:18 ` Chris Murphy
2014-02-11 3:15 ` Saint Germain
2014-02-11 6:59 ` Duncan
2014-02-11 10:04 ` Saint Germain
2014-02-11 20:35 ` Duncan
2014-02-12 17:16 ` Saint Germain [this message]
2014-02-11 17:33 ` UEFI/BIOS, was: " Chris Murphy
2014-02-11 7:47 ` Duncan
2014-02-11 17:21 ` Chris Murphy
2014-02-11 17:36 ` Saint Germain
2014-02-11 18:19 ` Chris Murphy
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=CAJbEPe6+3uH97z-oA-QCb-cCb_xDXb016YLP+gZM1wAdMk2KGw@mail.gmail.com \
--to=saintger@gmail.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).