From: Andrew Price <anprice@redhat.com>
To: cluster-devel.redhat.com
Subject: [Cluster-devel] [PATCH] GFS2: Add a next-resource-group pointer to resource groups
Date: Tue, 12 Jan 2016 15:23:39 +0000 [thread overview]
Message-ID: <56951A7B.5030201@redhat.com> (raw)
In-Reply-To: <CAHc6FU54vp6BsWfe+0Ea4a41c+kuehqKyLrBcVZFPxtsBWCY_A@mail.gmail.com>
On 12/01/16 13:30, Andreas Gruenbacher wrote:
> Is it guaranteed that the kernel will never set the new rg_skip field
> if it hasn't verified that the next resource group is where it thinks
> it is?
No, but rg_skip is set from the ri_addr of the next resource group in
the rindex and gfs2 generally trusts the rindex so if it's corrupt then
there'll be other problems down the line.
> Otherwise we could end up with incorrect fsck "hints" for
> corrupted filesystems, which would make things worse.
I don't think it would make things worse. fsck.gfs2 will be able to
check whether the rg_skip field is correct by checking it against the
rindex and whether there's an rgrp where it's pointing (and checking
that it's within a sensible range). Before, we only had the rindex and
the rgrp header to check against each other but now we have a third factor.
That said, the fsck.gfs2 case is only one of the ways this would be
useful. The original plan was to generally reduce dependence on the
rindex, effectively allowing us to iterate over all rgrps without
reading it in. Though I don't recall the specific issue which motivated
it, I can think of cases where it would improve things.
Andy
next prev parent reply other threads:[~2016-01-12 15:23 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-01-12 11:39 [Cluster-devel] [PATCH] GFS2: Add a next-resource-group pointer to resource groups Andrew Price
2016-01-12 11:47 ` Steven Whitehouse
2016-01-12 12:03 ` [Cluster-devel] [PATCH v2] " Andrew Price
2016-01-12 15:50 ` Bob Peterson
2017-02-02 14:57 ` Andrew Price
2017-02-13 17:59 ` [Cluster-devel] [PATCH v3] " Andrew Price
2017-02-13 18:06 ` Andrew Price
2017-02-14 10:32 ` Steven Whitehouse
2017-02-15 18:15 ` Andreas Gruenbacher
2016-01-12 12:39 ` [Cluster-devel] [PATCH] " Andreas Gruenbacher
2016-01-12 13:12 ` Andrew Price
2016-01-12 13:30 ` Andreas Gruenbacher
2016-01-12 15:23 ` Andrew Price [this message]
2017-02-15 17:40 ` Andreas Gruenbacher
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=56951A7B.5030201@redhat.com \
--to=anprice@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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.