From: dima <dolenin@parallels.com>
To: linux-btrfs@vger.kernel.org
Subject: Re: Best Practice - Partition, or not?
Date: Wed, 01 May 2013 17:50:38 +0900 [thread overview]
Message-ID: <5180D75E.4030605@parallels.com> (raw)
In-Reply-To: <201305011844.07087.russell@coker.com.au>
On 05/01/2013 05:44 PM, Russell Coker wrote:
> On Wed, 1 May 2013, dima <dolenin@parallels.com> wrote:
>>> If I want to manage a complete disk with btrfs, what's the "Best
>>> Practice"? Would it be best to create the btrfs filesystem on
>>> "/dev/sdb", or would it be better to create just one partition from
>>> start to end and then do "mkfs.btrfs /dev/sdb1"?
>>>
>>> Would the same recomendation hold true, if we're talking about huge
>>> disks, like 4TB or so?
>
> My biggest BTRFS array is a RAID-1 of 2*3TB disks. The system in question
> boots from an Intel SSD so I have no need of boot support on the hard disks.
>
>> (NB: grub will not boot from "/dev/sdb", selinux will)
>
> Not sure what you mean here, but SE Linux isn't a boot loader. Did you mean
> syslinux? That's a boot loader but I don't know if it works in such a
> configuration.
>
gosh! of course, SYSLINUX. Sorry guys.
(i am working with selinux just now that is why....)
Yes, syslinux will work, I had an install with root btrfs with syslinux
as a bootloader (at the time when grub2 did not support booting from btrfs)
next prev parent reply other threads:[~2013-05-01 8:50 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-05-01 7:51 Best Practice - Partition, or not? Alexander Skwar
2013-05-01 7:59 ` dima
2013-05-01 8:37 ` Alexander Skwar
2013-05-01 8:44 ` Russell Coker
2013-05-01 8:50 ` dima [this message]
2013-05-01 8:00 ` Hugo Mills
2013-05-01 8:46 ` Helmut Hullen
2013-05-08 7:31 ` Kai Krakow
2013-05-08 16:58 ` George Mitchell
2013-05-01 9:16 ` Gabriel de Perthuis
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=5180D75E.4030605@parallels.com \
--to=dolenin@parallels.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 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.