From: Josef Bacik <jbacik@fusionio.com>
To: Chris Murphy <lists@colorremedies.com>
Cc: Josef Bacik <jbacik@fusionio.com>,
Btrfs BTRFS <linux-btrfs@vger.kernel.org>
Subject: Re: regression, can't move subvols into subvols
Date: Wed, 9 Oct 2013 13:23:25 -0400 [thread overview]
Message-ID: <20131009172325.GH16461@localhost.localdomain> (raw)
In-Reply-To: <03A8C5A5-6E1D-45EC-9B1A-D0F144003580@colorremedies.com>
On Wed, Oct 09, 2013 at 11:17:43AM -0600, Chris Murphy wrote:
>
> On Oct 9, 2013, at 10:27 AM, Josef Bacik <jbacik@fusionio.com> wrote:
>
> > On Tue, Oct 08, 2013 at 03:58:23PM -0600, Chris Murphy wrote:
> >> I don't think this is expected, is it? I can no longer move a subvolume into another subvolume. I can move a subvolume into a directory. This happens with 3.11.3, and 3.12 rc4. I'm not sure yet when the regression first appeared.
> >>
> >> Example move subvol to subvol, where home is a subvolume that contains files, and f20inprogress is a newly created (empty) subvolume.
> >>
> >> [root@f20s btrfs]# mv home f20inprogress
> >> mv: cannot move ‘home’ to ‘f20inprogress/home’: File exists
> >>
> >
> > Fixed it with
> >
> > [PATCH] Btrfs: use right root when checking for hash collision
> >
> > Sorry about that.
>
> This behavior seems to go back quite far. At least 3.9.5 is affected; 3.9 is EOL but does it make sense to fix this for 3.10 and 3.11?
>
Yeah I'll mark it for stable. Thanks,
Josef
prev parent reply other threads:[~2013-10-09 17:23 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-10-08 21:58 regression, can't move subvols into subvols Chris Murphy
2013-10-08 22:29 ` Chris Murphy
2013-10-08 23:35 ` regression, can't move subvols into subvols, fs/btrfs/inode.c:8049 btrfs_rename Chris Murphy
2013-10-09 1:06 ` regression, can't move subvols into subvols Zach Brown
2013-10-09 16:27 ` Josef Bacik
2013-10-09 17:17 ` Chris Murphy
2013-10-09 17:23 ` Josef Bacik [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=20131009172325.GH16461@localhost.localdomain \
--to=jbacik@fusionio.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).