From: Karl Kiniger <karl.kiniger@med.ge.com>
To: linux-btrfs@vger.kernel.org
Subject: Why cannot I move a read-only snapshot around?
Date: Thu, 24 Oct 2013 17:29:56 +0200 [thread overview]
Message-ID: <20131024152955.GA6110@kipc2.localdomain> (raw)
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 682 Oct 24 16:01 @20131001
drwxr-xr-x. 1 root root 682 Oct 24 16:07 @20131004
drwxr-xr-x. 1 root root 682 Oct 24 16:10 @20131008
drwxr-xr-x. 1 root root 682 Oct 24 16:16 @20131010
drwxr-xr-x. 1 root root 682 Oct 24 16:23 @20131014
drwxr-xr-x. 1 root root 706 Oct 24 16:24 @20131018
drwxr-xr-x. 1 root root 706 Oct 24 16:31 @20131021
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
I know I can create other new ro snapshots within the readonly directory
and then delete those above but in the future I want to send/receive based on
those snapshots (send -p .... -c .... -c ....) but I want to move them
to a more convenient place.
How can I move them without re-sending all?
Karl
next reply other threads:[~2013-10-24 15:34 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-10-24 15:29 Karl Kiniger [this message]
2013-10-24 15:37 ` Why cannot I move a read-only snapshot around? Karl Kiniger
2013-10-24 17:10 ` Chris Murphy
2013-10-24 21:57 ` Karl Kiniger
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=20131024152955.GA6110@kipc2.localdomain \
--to=karl.kiniger@med.ge.com \
--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).