linux-btrfs.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Daniel Pocock <daniel@pocock.com.au>
To: linux-btrfs@vger.kernel.org
Subject: raw partition or LV for btrfs?
Date: Sun, 12 Aug 2012 16:46:52 +0000	[thread overview]
Message-ID: <5027DDFC.60504@pocock.com.au> (raw)



I notice this question on the wiki/faq:


https://btrfs.wiki.kernel.org/index.php/UseCases#What_is_best_practice_when_partitioning_a_device_that_holds_one_or_more_btr-filesystems

and as it hasn't been answered, can anyone make any comments on the subject

Various things come to mind:

a) partition the disk, create an LVM partition, and create lots of small
LVs, format each as btrfs

b) partition the disk, create an LVM partition, and create one big LV,
format as btrfs, make subvolumes

c) what about using btrfs RAID1?  Does either approach (a) or (b) seem
better for someone who wants the RAID1 feature?

d) what about booting from a btrfs system?  Is it recommended to follow
the ages-old practice of keeping a real partition of 128-500MB,
formatting it as btrfs, even if all other data is in subvolumes as per (b)?


             reply	other threads:[~2012-08-12 16:52 UTC|newest]

Thread overview: 14+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2012-08-12 16:46 Daniel Pocock [this message]
2012-08-12 22:48 ` raw partition or LV for btrfs? Fajar A. Nugraha
2012-08-13  4:19   ` Kyle Gates
2012-08-13  4:49     ` Fajar A. Nugraha
2012-08-14 11:23   ` Calvin Walton
2012-08-22 15:42     ` David Sterba
2012-08-28 11:54       ` raw partition or LV for btrfs? (FAQ updated) Daniel Pocock
2012-08-14 13:28   ` raw partition or LV for btrfs? Daniel Pocock
2012-08-14 13:52     ` Olivier Bonvalet
2012-08-14 13:53     ` Fajar A. Nugraha
2012-08-14 14:09       ` cwillu
2012-08-14 14:21         ` Fajar A. Nugraha
2012-08-14 14:50           ` cwillu
2012-08-14 14:44         ` Calvin Walton

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=5027DDFC.60504@pocock.com.au \
    --to=daniel@pocock.com.au \
    --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).