From: Eric Sandeen <sandeen@redhat.com>
To: Austin S Hemmelgarn <ahferroin7@gmail.com>,
Qu Wenruo <quwenruo@cn.fujitsu.com>,
Russell Coker <russell@coker.com.au>
Cc: Chris Mason <clm@fb.com>, Hugo Mills <hugo@carfax.org.uk>,
Btrfs mailing list <linux-btrfs@vger.kernel.org>
Subject: Re: Bug/regression: Read-only mount not read-only
Date: Wed, 2 Dec 2015 16:48:27 -0600 [thread overview]
Message-ID: <565F753B.5020000@redhat.com> (raw)
In-Reply-To: <565F2EF7.5000109@gmail.com>
On 12/2/15 11:48 AM, Austin S Hemmelgarn wrote:
> On a side note, do either XFS or ext4 support removing the norecovery
> option from the mount flags through mount -o remount? Even if they
> don't, that might be a nice feature to have in BTRFS if we can safely
> support it.
It's not remountable today on xfs:
/* ro -> rw */
if ((mp->m_flags & XFS_MOUNT_RDONLY) && !(*flags & MS_RDONLY)) {
if (mp->m_flags & XFS_MOUNT_NORECOVERY) {
xfs_warn(mp,
"ro->rw transition prohibited on norecovery mount");
return -EINVAL;
}
not sure about ext4.
-Eric
next prev parent reply other threads:[~2015-12-02 22:48 UTC|newest]
Thread overview: 24+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-11-28 13:46 Bug/regression: Read-only mount not read-only Hugo Mills
2015-11-30 14:59 ` Austin S Hemmelgarn
2015-11-30 15:28 ` Hugo Mills
2015-11-30 16:00 ` Austin S Hemmelgarn
2015-11-30 16:48 ` Chris Mason
2015-11-30 17:06 ` Hugo Mills
2015-12-01 19:00 ` Chris Mason
2015-12-01 19:05 ` Eric Sandeen
2015-12-02 6:25 ` Russell Coker
2015-12-02 9:06 ` Qu Wenruo
2015-12-02 9:23 ` Qu Wenruo
2015-12-02 16:54 ` Eric Sandeen
2015-12-02 17:48 ` Austin S Hemmelgarn
2015-12-02 18:53 ` Hugo Mills
2015-12-02 22:48 ` Eric Sandeen [this message]
2015-12-02 23:40 ` Qu Wenruo
2015-12-02 23:51 ` Hugo Mills
2015-12-03 6:44 ` Duncan
2015-12-04 12:32 ` Austin S Hemmelgarn
2015-12-04 12:23 ` Austin S Hemmelgarn
2015-11-30 17:08 ` Austin S Hemmelgarn
2015-12-01 6:46 ` Qu Wenruo
2015-12-01 18:54 ` Chris Mason
2015-12-01 23:47 ` Qu Wenruo
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=565F753B.5020000@redhat.com \
--to=sandeen@redhat.com \
--cc=ahferroin7@gmail.com \
--cc=clm@fb.com \
--cc=hugo@carfax.org.uk \
--cc=linux-btrfs@vger.kernel.org \
--cc=quwenruo@cn.fujitsu.com \
--cc=russell@coker.com.au \
/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