All of lore.kernel.org
 help / color / mirror / Atom feed
From: Hullen@t-online.de (Helmut Hullen)
To: linux-btrfs@vger.kernel.org
Subject: Re: Best Practice - Partition, or not?
Date: 01 May 2013 10:46:00 +0200	[thread overview]
Message-ID: <CW2IaniPCXB@helmut.hullen.de> (raw)
In-Reply-To: <loom.20130501T094600-451@post.gmane.org>

Hallo, Alexander,

Du meintest am 01.05.13:

> 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?

I've tested both versions on a 3 disk bundle of 3 TByte disks (data  
raid0, meta raid1).

  mkfs.btrfs ... /dev/sdb /dev/sdc /dev/sdd

made some more problems, especially when recognizing or deleting the  
disk(s). Maybe that's a problem more related to "util-linux" (especially  
"wipefs" and "blkid").

Partitioning first with gdisk and then

  mkfs.btrfs ... /dev/sdb1 /dev/sdc1 /dev/sdd1

runs better (perhaps without problems).

Viele Gruesse!
Helmut

  parent reply	other threads:[~2013-05-01  8:47 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
2013-05-01  8:00 ` Hugo Mills
2013-05-01  8:46 ` Helmut Hullen [this message]
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=CW2IaniPCXB@helmut.hullen.de \
    --to=hullen@t-online.de \
    --cc=helmut@hullen.de \
    --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.