From: Eric Sandeen <sandeen@redhat.com>
To: linux-xfs <linux-xfs@vger.kernel.org>
Subject: [PATCH 0/2] xfs: readonly handling changes
Date: Thu, 9 Mar 2017 13:40:41 -0600 [thread overview]
Message-ID: <bbb0243d-e491-02e0-1802-e95cba4e8486@redhat.com> (raw)
A couple of changes to how xfs behaves w.r.t. readonly
mounts.
1) remove readonly checks from xfs_release and xfs_inactive paths
2) write unmount record even for RO mounts (which may have done recovery)
Both of these stem from the fact that a readonly mount (as opposed to a
ro,norecovery mount) is /not/ guaranteed to do no writes to the block
device; in fact we do that straightaway when we replay the log. Other
"OMG don't write!" leftovers linger, and cause issues as described
in the following 2 patches.
Dave suggested grand plans for coalescing more of this into common
paths ala remount handling, i.e. a RO mount gets mounted RW and then
just goes through the same transition to RO at the end, but I haven't
put all that together yet, and these patches address a couple bugs in
a more targeted fashion until that can happen.
-Eric
next reply other threads:[~2017-03-09 19:41 UTC|newest]
Thread overview: 15+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-03-09 19:40 Eric Sandeen [this message]
2017-03-09 20:15 ` [PATCH 1/2] xfs: write unmount record for ro mounts Eric Sandeen
2017-03-15 15:18 ` Brian Foster
2017-03-09 20:24 ` [PATCH 2/2] xfs: remove readonly checks from xfs_release & xfs_inactive Eric Sandeen
2017-03-09 20:39 ` Eric Sandeen
2017-03-13 13:23 ` Brian Foster
2017-03-13 22:16 ` Eric Sandeen
2017-03-14 11:35 ` Brian Foster
2017-03-14 23:23 ` [PATCH 2/2 V2] xfs: toggle readonly state around xfs_log_mount_finish Eric Sandeen
2017-03-15 11:36 ` Brian Foster
2017-03-16 19:15 ` Darrick J. Wong
2017-03-16 23:42 ` Dave Chinner
2017-03-16 23:52 ` Eric Sandeen
2017-03-18 7:38 ` Dave Chinner
2017-03-27 17:16 ` Darrick J. Wong
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=bbb0243d-e491-02e0-1802-e95cba4e8486@redhat.com \
--to=sandeen@redhat.com \
--cc=linux-xfs@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).