From: Karl Kiniger <karl.kiniger@med.ge.com>
To: Chris Murphy <lists@colorremedies.com>
Cc: Btrfs BTRFS <linux-btrfs@vger.kernel.org>
Subject: Re: Why cannot I move a read-only snapshot around?
Date: Thu, 24 Oct 2013 23:57:15 +0200 [thread overview]
Message-ID: <20131024215715.GA14128@kipc2.localdomain> (raw)
In-Reply-To: <1D7328F7-EB4F-4C3F-8EAB-2EDB6331F77E@colorremedies.com>
Hi,
On Thu 131024, Chris Murphy wrote:
>
> On Oct 24, 2013, at 9:29 AM, Karl Kiniger <karl.kiniger@med.ge.com> wrote:
>
> > Dear list, (newbie alert)
> >
> > After sucessfully sending and receiving a dozen of related snapshots
> > I want to move them all to the readonly folder but I cannot:
> >
> > ls -l
> > .....
......
> > drwxr-xr-x. 1 root root 734 Oct 24 16:36 @20131023
> > drwxr-xr-x. 1 root root 734 Oct 24 16:41 @20131024
> > drwxr-xr-x. 1 root root 734 Oct 24 16:41 F19
> > drwxr-xr-x. 1 root root 0 Oct 24 17:21 readonly
> >
> >
> > mv \@20131024 readonly
> >
> > mv: cannot move ‘@20131024’ to ‘readonly/@20131024’: Read-only file system
>
> Are the @ snapshot read only snapshots? And is read only just a regular directory?
Yes they are read only snapshots (just received by btrfs receive) and
"readonly" is a regular directory. I deliberately did not try to move
those snapshots into other snapshots.
I can move r/w snapshots around without problems
(into some regular directory), just the r/o snapshots refuse moving.
cat /proc/version
Linux version 3.11.6-200.fc19.x86_64
Still curious,
Karl
>
> I don't know that this is a bug, it seems like it could be intentional because a read only file system wouldn't let you move it out of one tree into another. But there was a bug that prevented moving of subvolumes into subvolumes (untested if moving subvolumes into folders worked) that was fixed in kernel 3.11.6 so that might be worth a shot.
>
>
> 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
next prev parent reply other threads:[~2013-10-24 21:56 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-10-24 15:29 Why cannot I move a read-only snapshot around? Karl Kiniger
2013-10-24 15:37 ` Karl Kiniger
2013-10-24 17:10 ` Chris Murphy
2013-10-24 21:57 ` Karl Kiniger [this message]
2013-10-24 22:28 ` Chris Murphy
2013-10-24 22:46 ` Karl Kiniger
2013-10-24 22:51 ` Chris Murphy
2013-10-24 23:13 ` Karl Kiniger
2013-10-25 0:57 ` Chris Murphy
2013-10-25 8:00 ` Karl Kiniger
2013-10-24 18:05 ` Duncan
2013-10-24 22:09 ` Karl Kiniger
2013-10-26 5:45 ` Christian Robert
2013-10-28 11:56 ` Karl Kiniger
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=20131024215715.GA14128@kipc2.localdomain \
--to=karl.kiniger@med.ge.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).