From: Abhi Das <adas@redhat.com>
To: cluster-devel.redhat.com
Subject: [Cluster-devel] [PATCH v3 0/3] gfs2: local statfs improvements
Date: Tue, 20 Oct 2020 15:58:02 -0500 [thread overview]
Message-ID: <20201020205805.5705-1-adas@redhat.com> (raw)
This patchset allows gfs2 to sync statfs info from the journal to the
master statfs file during a log flush or during recovery. We still
write to the local statfs file to allow older versions to recover the
statfs info of newer kernels with this patchset.
This version addresses the bug Andreas found with xfstests:generic/034.
Turns out we weren't looking up the statfs inodes early enough in the
mount process. I also added some comments in the code.
Abhi Das (3):
gfs2: Add fields for statfs info in struct gfs2_log_header_host
gfs2: lookup local statfs inodes prior to journal recovery
gfs2: Recover statfs info in journal head
fs/gfs2/incore.h | 12 ++++
fs/gfs2/lops.c | 2 +-
fs/gfs2/lops.h | 1 +
fs/gfs2/ops_fstype.c | 133 +++++++++++++++++++++++++++++++------------
fs/gfs2/recovery.c | 108 +++++++++++++++++++++++++++++++++++
fs/gfs2/super.c | 33 ++++++++++-
fs/gfs2/super.h | 5 ++
7 files changed, 256 insertions(+), 38 deletions(-)
--
2.20.1
next reply other threads:[~2020-10-20 20:58 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-10-20 20:58 Abhi Das [this message]
2020-10-20 20:58 ` [Cluster-devel] [PATCH v3 1/3] gfs2: Add fields for statfs info in struct gfs2_log_header_host Abhi Das
2020-10-20 20:58 ` [Cluster-devel] [PATCH v3 2/3] gfs2: lookup local statfs inodes prior to journal recovery Abhi Das
2020-10-20 20:58 ` [Cluster-devel] [PATCH v3 3/3] gfs2: Recover statfs info in journal head Abhi Das
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=20201020205805.5705-1-adas@redhat.com \
--to=adas@redhat.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).