From: Jose Otero <jose.manuel.otero@gmail.com>
To: linux-btrfs@vger.kernel.org
Subject: Raid 0 setup doubt.
Date: Sun, 27 Mar 2016 12:35:43 +0200 [thread overview]
Message-ID: <56F7B77F.9050306@gmail.com> (raw)
Hello,
--------------------------------------
I apologize beforehand if I'm asking a too basic question for the
mailing list, or if it has been already answered at nauseam.
--------------------------------------
I have two hdd (Western Digital 750 GB approx. 700 GiB each), and I
planning to set up a RAID 0 through btrfs. UEFI firmware/boot, no dual
boot, only linux.
My question is, given the UEFI partition plus linux swap partition, I
won't have two equal sized partitions for setting up the RAID 0 array.
So, I'm not quite sure how to do it. I'll have:
/dev/sda:
16 KiB (GPT partition table)
sda1: 512 MiB (EFI, fat32)
sda2: 16 GiB (linux-swap)
sda3: rest of the disk / (btrfs)
/dev/sdb:
sdb1: (btrfs)
The btrfs partitions on each hdd are not of the same size (admittedly by
an small difference, but still). Even if a backup copy of the EFI
partition is created in the second hdd (i.e. sdb) which it may be, not
sure, because the linux-swap partion is still left out.
Should I stripe both btrfs partitions together no matter the size?
mkfs.btrfs -m raid0 -d raid0 /dev/sda3 /dev/sdb1
How will btrfs manage the difference in size?
Or should I partition out the extra size of /dev/sdb for trying to match
equally sized partions? in other words:
/dev/sdb:
sdb1: 17 GiB approx. free or for whatever I want.
sdb2: (btrfs)
and then:
mkfs.btrfs -m raid0 -d raid0 /dev/sda3 /dev/sdb2
Again, I'm sorry if it's an idiotic question, but I don't have it quite
clear and I would like to do it properly. So, any hint from more
knowable users would be MUCH appreciate it.
Thanks in advance.
JM.
next reply other threads:[~2016-03-27 10:35 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-03-27 10:35 Jose Otero [this message]
2016-03-28 0:56 ` Raid 0 setup doubt Duncan
2016-03-28 5:26 ` James Johnston
2016-03-28 8:51 ` Duncan
2016-03-28 12:35 ` Austin S. Hemmelgarn
2016-03-29 1:46 ` Duncan
2016-03-29 2:10 ` Chris Murphy
2016-03-28 20:30 ` Jose Otero
2016-03-29 4:14 ` Duncan
2016-03-28 2:42 ` Chris Murphy
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=56F7B77F.9050306@gmail.com \
--to=jose.manuel.otero@gmail.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;
as well as URLs for NNTP newsgroup(s).