Linux Btrfs filesystem development
 help / color / mirror / Atom feed
From: dima <dolenin@parallels.com>
To: <linux-btrfs@vger.kernel.org>
Subject: Re: What is best practice when partitioning a device that holds one or more btr-filesystems
Date: Thu, 15 Dec 2011 10:09:01 +0900	[thread overview]
Message-ID: <4EE948AD.9040001@parallels.com> (raw)
In-Reply-To: <CAKsPgxG7yr3SzwJYdsS58dMxZ_DwWH6b1CLg0eXwDmfQNAY4XA@mail.gmail.com>

On 12/15/2011 03:51 AM, Wilfred van Velzen wrote:
> On Wed, Dec 14, 2011 at 7:21 PM, Mitch Harder
> <mitch.harder@sabayonlinux.org>  wrote:
>> On Wed, Dec 14, 2011 at 7:00 AM, Wilfred van Velzen<wvvelzen@gmail.com>  wrote:
>>>
>>> What is best practice when partitioning a device that holds one or
>>> more btr-filesystems
>>>
>>
>> When it comes to "best practices" in btrfs filesystem layouts, your
>> primary consideration should be to make yourself robust to potential
>> filesystem failure.
>>
>> Of course this should be true of any storage arrangement.
>>
>> But if you're going to be playing with rc kernels and applying patches
>> off the list, you might want to break it up into multiple partitions
>> so as to mitigate the problem if one partition picks up a
>> inconsistency.
>>
>> On the other hand, it's also good for people to use the volume and
>> subvolume features.  There's many different ways for people to make
>> use of volumes and subvolumes, and it's good to explore those
>> features.
>
> Well, of course there are different usecases for different situations.
>
> What I want to find out is, if you should partition differently when
> you are using btrfs compared to partitioning for the other
> older/regular filesystems for linux, for regular (production)
> usecases.

Maybe just skip partitioning altogether ;)  - format the device to btrfs 
and use subvolumes instead of your usual partitions (some /boot 
restrictions apply). You won't be able to use grub2 though, but syslinux 
will work.

  parent reply	other threads:[~2011-12-15  1:09 UTC|newest]

Thread overview: 11+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2011-12-14 13:00 What is best practice when partitioning a device that holds one or more btr-filesystems Wilfred van Velzen
2011-12-14 13:17 ` Helmut Hullen
2011-12-14 16:43 ` Peeters Simon
     [not found] ` <CAKcLGm-LZmyOKm4gegZDRYaq-DO-KW+5CCb_E7n8WvF0fEFCeQ@mail.gmail.com>
2011-12-14 18:51   ` Wilfred van Velzen
     [not found]     ` <CA+WRLO98Je2J1SMZv0zVi1r1AfGFcnUCHKU=sJAsYDuUssqx8w@mail.gmail.com>
2011-12-14 21:42       ` Wilfred van Velzen
2011-12-14 22:46         ` Fajar A. Nugraha
2011-12-15  0:42         ` Kok, Auke-jan H
2011-12-15  1:09     ` dima [this message]
2011-12-15  8:25       ` Sander
2011-12-15  8:29         ` dima
2011-12-15  8:55           ` Sander

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=4EE948AD.9040001@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