From: Duncan <1i5t5.duncan@cox.net>
To: linux-btrfs@vger.kernel.org
Subject: Re: Mixed and raid [was Re: BUG: btrfsRe: Does btrfs "raid1" actually provide any resilience?]
Date: Fri, 15 Nov 2013 07:12:50 +0000 (UTC) [thread overview]
Message-ID: <pan$afa55$861f820e$b8e2b567$4f5d324c@cox.net> (raw)
In-Reply-To: 52853ED2.8040606@libero.it
Goffredo Baroncelli posted on Thu, 14 Nov 2013 22:21:22 +0100 as
excerpted:
> after some tests and looking at the code I discovered that the current
> mkfs.btrfs doesn't allow any raid profile other than SINGLE for data and
> meta-data when the mixed metadata/data group is enabled.
That'd be a big problem for me, here, as I run a separate sub-GiB (640
MiB) btrfs filesystem /var/log, in data+metadata raid1 mode. (The
mountpoint is actually /lg, with /var/log a symlink pointing at it.)
btrfs f sh /lg
Label: lg0238gcnx+35l0 uuid: c77a9eb8-9841-4c2b-925e-75d0a925dcc3
Total devices 2 FS bytes used 51.93MiB
devid 1 size 640.00MiB used 288.00MiB path /dev/sdc4
devid 2 size 640.00MiB used 288.00MiB path /dev/sda4
btrfs f df /lg
System, RAID1: total=32.00MiB, used=4.00KiB
Data+Metadata, RAID1: total=256.00MiB, used=51.92MiB
I've had a couple bad shutdowns, but btrfs scrub has reliably cleaned up
the resulting mess on /lg due to open logfiles, and I'd be rather unhappy
if that weren't possible.
Meanwhile, I also have two separate sub-GiB (256 MiB) /boot filesystems,
one on each (of two) SSDs, with the grub2 on each pointing at its own
/boot so a broken grub2 update won't break my ability to boot.
Those are both data+metadata dup mode:
btrfs f df /bt
System, DUP: total=8.00MiB, used=4.00KiB
System, single: total=4.00MiB, used=0.00
Data+Metadata, DUP: total=114.00MiB, used=41.38MiB
Data+Metadata, single: total=8.00MiB, used=0.00
You're saying data+metadata DUP wouldn't be possible here either, which
would make me pretty unhappy too.
Fortunately I did those mkfs.btrfs on an earlier btrfs-tools so wasn't
affected by this bug, but bug I would indeed call it, for sure!
--
Duncan - List replies preferred. No HTML msgs.
"Every nonfree program has a lord, a master --
and if you use the program, he is your master." Richard Stallman
next prev parent reply other threads:[~2013-11-15 7:13 UTC|newest]
Thread overview: 16+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-11-14 11:02 Does btrfs "raid1" actually provide any resilience? Lutz Vieweg
2013-11-14 17:18 ` George Mitchell
2013-11-14 17:35 ` Lutz Vieweg
2013-11-14 19:59 ` Kyle Gates
2013-11-15 1:58 ` George Mitchell
2013-11-14 18:22 ` Goffredo Baroncelli
2013-11-14 20:47 ` BUG: btrfsRe: " Goffredo Baroncelli
2013-11-14 21:21 ` Mixed and raid [was Re: BUG: btrfsRe: Does btrfs "raid1" actually provide any resilience?] Goffredo Baroncelli
2013-11-15 4:44 ` Anand Jain
2013-11-15 10:35 ` Lutz Vieweg
2013-11-15 10:36 ` Lutz Vieweg
2013-11-15 7:12 ` Duncan [this message]
2013-11-15 7:30 ` Goffredo Baroncelli
2013-11-15 9:37 ` Duncan
2013-11-14 21:22 ` BUG: btrfsRe: Does btrfs "raid1" actually provide any resilience? Chris Murphy
2013-11-14 21:31 ` Goffredo Baroncelli
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='pan$afa55$861f820e$b8e2b567$4f5d324c@cox.net' \
--to=1i5t5.duncan@cox.net \
--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).