From: Qu Wenruo <quwenruo@cn.fujitsu.com>
To: Chris Murphy <lists@colorremedies.com>,
Btrfs BTRFS <linux-btrfs@vger.kernel.org>
Subject: Re: [bug] <subvol> doesn't belong to btrfs mount point
Date: Thu, 18 Sep 2014 14:26:19 +0800 [thread overview]
Message-ID: <541A7B0B.4010503@cn.fujitsu.com> (raw)
In-Reply-To: <D8984BA0-E220-4D74-AADC-5C488023EDA1@colorremedies.com>
I am very sorry that my commit caused the problem.
In fact some users have already find the problem and I sent the fix some
time ago.
The patch is https://patchwork.kernel.org/patch/4842201/
Hopes this helps.
Thanks,
Qu
-------- Original Message --------
Subject: Re: [bug] <subvol> doesn't belong to btrfs mount point
From: Chris Murphy <lists@colorremedies.com>
To: Btrfs BTRFS <linux-btrfs@vger.kernel.org>
Date: 2014年09月16日 10:08
> On Sep 12, 2014, at 5:39 PM, Chris Murphy <lists@colorremedies.com> wrote:
>
>> Summary: When a btrfs subvolume is mounted with -o subvol, and a nested ro subvol/snapshot is created, btrfs send returns with an error. If the top level (id 5) is mounted instead, the send command succeeds.
> I'm not able to reproduce this, so at the moment I'm going to say it's user error until I can.
>
>
> Chris Murphy--
> To unsubscribe from this list: send the line "unsubscribe linux-btrfs" in
> the body of a message to majordomo@vger.kernel.org
> More majordomo info at http://vger.kernel.org/majordomo-info.html
prev parent reply other threads:[~2014-09-18 6:26 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-09-12 23:39 [bug] <subvol> doesn't belong to btrfs mount point Chris Murphy
2014-09-16 2:08 ` Chris Murphy
2014-09-18 6:26 ` Qu Wenruo [this message]
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=541A7B0B.4010503@cn.fujitsu.com \
--to=quwenruo@cn.fujitsu.com \
--cc=linux-btrfs@vger.kernel.org \
--cc=lists@colorremedies.com \
/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).