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 13:12:20 +0000 [thread overview]
Message-ID: <5694FBB4.7040007@redhat.com> (raw)
In-Reply-To: <CAHc6FU4zvnws2U2Ytz1Lx4B_NCcAys9nq7Y6-uRonxMy2GA4oA@mail.gmail.com>
On 12/01/16 12:39, Andreas Gruenbacher wrote:
> On Tue, Jan 12, 2016 at 12:39 PM, Andrew Price <anprice@redhat.com> wrote:
>> Add a new rg_skip field to struct gfs2_rgrp, replacing __pad. The
>> rg_skip field has the following meaning:
>>
>> - If rg_skip is zero, it is considered unset and not useful.
>> - If rg_skip is non-zero, its value will be the number of blocks between
>> this rgrp's address and the next rgrp's address. This can be used as a
>> hint by fsck.gfs2 when rebuilding a bad rindex, for example.
>
> How is that better than a resource group size field that wouldn't need
> to special case the last resource group?
The last block of the mapped space in a resource group (ri_data0 +
ri_data) is not necessarily at the block address immediately preceding
the next resource group, due to device alignment and bitmap rounding.
Also, if we assume we know the position of the first new resource group
that would be created by gfs2_grow then we might get it wrong, so we
can't set the final resource group's rg_skip to a useful value.
Andy
next prev parent reply other threads:[~2016-01-12 13:12 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 [this message]
2016-01-12 13:30 ` Andreas Gruenbacher
2016-01-12 15:23 ` Andrew Price
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=5694FBB4.7040007@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.