linux-btrfs.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Goffredo Baroncelli <kreijack@libero.it>
To: Duncan <1i5t5.duncan@cox.net>
Cc: linux-btrfs@vger.kernel.org, Anand Jain <anand.jain@oracle.com>
Subject: Re: Mixed and raid [was Re: BUG: btrfsRe: Does btrfs "raid1" actually provide any resilience?]
Date: Fri, 15 Nov 2013 08:30:49 +0100	[thread overview]
Message-ID: <5285CDA9.3020208@libero.it> (raw)
In-Reply-To: <pan$afa55$861f820e$b8e2b567$4f5d324c@cox.net>

On 2013-11-15 08:12, Duncan wrote:
> 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.)
> 
[...]
> 
> You're saying data+metadata DUP wouldn't be possible here either, which 
> would make me pretty unhappy too.

The problem should be in mkfs.btrfs not in the btrfs kernel code. So if
the filesystem was created, there should be not problem.

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

Anand posted a patch few hours ago (which worked for me). I think that
this bug could be addressed quickly.

BR


-- 
gpg @keyserver.linux.it: Goffredo Baroncelli (kreijackATinwind.it>
Key fingerprint BBF5 1610 0B64 DAC6 5F7D  17B2 0EDA 9B37 8B82 E0B5

  reply	other threads:[~2013-11-15  7:30 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
2013-11-15  7:30         ` Goffredo Baroncelli [this message]
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=5285CDA9.3020208@libero.it \
    --to=kreijack@libero.it \
    --cc=1i5t5.duncan@cox.net \
    --cc=anand.jain@oracle.com \
    --cc=kreijack@inwind.it \
    --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).