From: Goldwyn Rodrigues <rgoldwyn@suse.de>
To: Btrfs BTRFS <linux-btrfs@vger.kernel.org>
Subject: mount policy for subvols if root is remount,ro
Date: Tue, 7 Mar 2017 07:59:53 -0600 [thread overview]
Message-ID: <b390c27c-224b-b48b-eec3-218635f90a0e@suse.de> (raw)
Hi,
I want to know if re-mounting the root filesystem read-only should
change subvolumes mounted as read-write to read-only as well? We do
allow mounting subvolumes RW _after_ the root filesystem is mounted RO.
# mount /dev/vdb /mnt
# mount -o ro,subvol=svro /dev/vdb /mnt/svro
# mount -o rw,subvol=svrw /dev/vdb /mnt/svrw
# mount -o remount,ro /dev/vdb /mnt
# touch /mnt/f3
touch: cannot touch '/mnt/f3': Read-only file system
Changes subvolume to read-only as well.
# touch /mnt/svrw/f3
touch: cannot touch '/mnt/svrw/f3': Read-only file system
However, remount of subvol as RW after remount,ro of root works:
# mount -o remount,rw,subvol=svrw /dev/vdb /mnt/svrw
# touch /mnt/svrw/f3
--
Goldwyn
next reply other threads:[~2017-03-07 13:59 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-03-07 13:59 Goldwyn Rodrigues [this message]
2017-03-08 12:03 ` mount policy for subvols if root is remount,ro Goldwyn Rodrigues
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=b390c27c-224b-b48b-eec3-218635f90a0e@suse.de \
--to=rgoldwyn@suse.de \
--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).