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: Fri, 25 Oct 2013 00:46:08 +0200 [thread overview]
Message-ID: <20131024224608.GA14904@kipc2.localdomain> (raw)
In-Reply-To: <97FC1966-5DC7-488F-8A6C-C8C8B2EB8490@colorremedies.com>
On Thu 131024, Chris Murphy wrote:
> dr--------. 1 chris chris 0 Oct 24 16:15 donotmove
>
> [chris@f20s ~]$ mv donotmove/ Videos/
> mv: cannot move ‘donotmove/’ to ‘Videos/donotmove’: Permission denied'
>
> I own that directory. But because it's read only, I can't move it because moving it changes it. Of course if I become root, that overrides posix permissions, but the readonly status of a subvolume isn't like posix permissions and I see now reason why root should be able to modify it. And moving it does modify it.
tries this all as root.
drwxr-xr-x. 1 root root 734 Oct 24 16:41 @20131024 (this is a r/o snap)
It looks to me similar to a read-only mounted filesystem:
pc2:/u2/F19/@20131024# touch foo
touch: cannot touch ‘foo’: Read-only file system
In what way would a r/o snapshot be modified because of moving its
"mount point" ? No one is ever doing something inside.
Karl
> Chris Murphy
next prev parent reply other threads:[~2013-10-24 22:45 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
2013-10-24 22:28 ` Chris Murphy
2013-10-24 22:46 ` Karl Kiniger [this message]
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=20131024224608.GA14904@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).