From: Alin Dobre <alin.dobre@elastichosts.com>
To: Duncan <1i5t5.duncan@cox.net>, linux-btrfs@vger.kernel.org
Subject: Re: Subvolume creation returns file exists
Date: Mon, 18 Nov 2013 13:22:12 +0000 [thread overview]
Message-ID: <528A1484.4030603@elastichosts.com> (raw)
In-Reply-To: <pan$e2b20$cd0040f6$ff39147c$2c522512@cox.net>
On 16/11/13 18:57, Duncan wrote:
> 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.
Thanks for all the info, Duncan.
Cheers,
Alin.
next prev parent reply other threads:[~2013-11-18 13:22 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
2013-11-18 13:22 ` Alin Dobre [this message]
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=528A1484.4030603@elastichosts.com \
--to=alin.dobre@elastichosts.com \
--cc=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).