From: Duncan <1i5t5.duncan@cox.net>
To: linux-btrfs@vger.kernel.org
Subject: Re: Subvolume creation returns file exists
Date: Sat, 16 Nov 2013 18:57:53 +0000 (UTC) [thread overview]
Message-ID: <pan$e2b20$cd0040f6$ff39147c$2c522512@cox.net> (raw)
In-Reply-To: pan$8331$e81056a3$92e0314$93218fd5@cox.net
Duncan posted on Fri, 15 Nov 2013 16:07:22 +0000 as excerpted:
> FWIW, here's the version string from my btrfs-progs, updated a couple
> days ago (tho there's one known bug in it, related to doing a mkfs.btrfs
> on a sub-GiB filesystem, patch posted to list but as I've not updated in
> a couple days I don't know whether it's in master yet).
>
> Btrfs v0.20-rc1-591-gc652e4e
FWIW, that patch is in now.
Btrfs v0.20-rc1-596-ge9ac73b
commit e9ac73b441b1b05b57ce99be1aff02eac6929448
Author: Anand Jain <Anand.Jain@oracle.com>
Date: Fri Nov 15 19:11:09 2013 +0800
btrfs-progs: for mixed group check opt before default raid profile is
enforced
This fixes the regression introduced with the patch
btrfs-progs: avoid write to the disk before sure to create fs
what happened with this patch is it missed the check to see if the
user has the option set before pushing the defaults.
--
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-16 18:58 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-11-15 14:33 Subvolume creation returns file exists Alin Dobre
2013-11-15 15:27 ` Hugo Mills
2013-11-15 16:39 ` cwillu
2013-11-15 16:07 ` Duncan
2013-11-16 18:57 ` Duncan [this message]
2013-11-18 13:22 ` Alin Dobre
2013-11-28 10:01 ` Alin Dobre
2013-11-29 5:40 ` Wang Shilong
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$e2b20$cd0040f6$ff39147c$2c522512@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 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.