From: Duncan <1i5t5.duncan@cox.net>
To: linux-btrfs@vger.kernel.org
Subject: Re: Questions about FIEMAP
Date: Wed, 28 Oct 2015 12:36:11 +0000 (UTC) [thread overview]
Message-ID: <pan$d8e7d$1b0b27e5$1154191$b17f2ea@cox.net> (raw)
In-Reply-To: CY1PR10MB0428CCC32D899CB0405B29ACE4210@CY1PR10MB0428.namprd10.prod.outlook.com
Wang, Zhiye posted on Wed, 28 Oct 2015 09:57:29 +0000 as excerpted:
> Thank you all for your comments.
>
> A further question is: if I mount a btrfs file system in "readonly"
> mode, will any operation cause the blocks of a file get changed?
Note that both bind-mounts and btrfs subvolume mounts can be used to make
parts of a filesystem appear in multiple locations in the filesystem
tree. Because these different mounts can be separately mounted read-only
or writable, there's no guarantee that just because a filesystem or part
of it is read-only mounted in one location, it's read-only mounted
everywhere it can be accessed, and thus no guarantee that files even on a
read-only mounted filesystem or subvolume won't actually change out from
under you.
However, bind-mounts in particular aren't btrfs specific, so just because
btrfs subvolumes add another case in which the above can be true, doesn't
mean bind-mounts can't be used on other filesystems to effect the same
sort of otherwise read-only file instabilities.
--
Duncan - List replies preferred. No HTML msgs.
"Every nonfree program has a lord, a master --
and if you use the program, he is your master." Richard Stallman
prev parent reply other threads:[~2015-10-28 12:36 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-10-12 4:37 Questions about FIEMAP Wang, Zhiye
2015-10-12 6:01 ` Duncan
2015-10-12 8:10 ` Hugo Mills
2015-10-12 13:04 ` David Sterba
2015-10-12 13:27 ` Eric Sandeen
2015-10-28 9:57 ` Wang, Zhiye
2015-10-28 12:36 ` Duncan [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='pan$d8e7d$1b0b27e5$1154191$b17f2ea@cox.net' \
--to=1i5t5.duncan@cox.net \
--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).