From: dima <dolenin@parallels.com>
To: linux-btrfs@vger.kernel.org
Subject: Re: Best Practice - Partition, or not?
Date: Wed, 01 May 2013 16:59:34 +0900 [thread overview]
Message-ID: <5180CB66.9030803@parallels.com> (raw)
In-Reply-To: <loom.20130501T094600-451@post.gmane.org>
On 05/01/2013 04:51 PM, Alexander Skwar wrote:
> Hello
>
> 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?
>
> Cross platform compatibility (OS X, Windows, FreeBSD, …) is of no matter to
> me.
>
> Thanks,
> Alexander
(NB: grub will not boot from "/dev/sdb", selinux will)
next prev parent reply other threads:[~2013-05-01 8:09 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 [this message]
2013-05-01 8:37 ` Alexander Skwar
2013-05-01 8:44 ` Russell Coker
2013-05-01 8:50 ` dima
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=5180CB66.9030803@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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox