cluster-devel.redhat.com archive mirror
 help / color / mirror / Atom feed
From: Andrew Price <anprice@redhat.com>
To: cluster-devel.redhat.com
Subject: [Cluster-devel] [PATCH 2/4] mkfs.gfs2: Align resource groups to RAID stripes
Date: Thu, 06 Jun 2013 16:17:51 +0100	[thread overview]
Message-ID: <51B0A81F.2010605@redhat.com> (raw)
In-Reply-To: <1370524289.2744.23.camel@menhir>

On 06/06/13 14:11, Steven Whitehouse wrote:
> It has never been valid to assume that all the rgrps are the same size.
> It may be useful as a hint, but we should not be relying on that being
> true. Obviously it makes sense to try and keep them to an even spacing
> where possible but we must allow for them to be placed and sized
> independently as required for alignment, etc.
>
> There are some restrictions on rgrp length as they need to be aligned
> such as to give an integer number of bitmap bytes, and in fact it would
> be good if that could be further enforced to ensure that all rgrp
> bitmaps are an integer number of 64 bit words in length (so a multiple
> of 32 blocks, excluding the headers). So depending on the various
> restrictions, there may be a few unused blocks between rgrps in some
> cases.

This is on my to-do list and should be a case of changing the "& 
~(uint32_t)3" parts of rgblocks2bitblocks() but I wanted to make sure 
that won't break fsck for older file systems first.

> It would be worth abstracting the details about alignment from mkfs in
> due course, so that fsck also has access to the same information about
> where rgrps are likely to have been put, I think.

Yes, I need to move the new rgrp creation bits from mkfs into libgfs2 
now so that's going to mean updating the other tools to use them 
eventually (hold onto your hats!).

> Some further thoughts:
>
>   - Would it be useful to introduce a flag to show the source of an rgrp
> (whether mkfs or gfs2_grow) ?
>   - Would it be useful to add a creation date stamp to each rgrp so that
> we can see when things have happened in the past?

Both sound good to me.

Andy



  parent reply	other threads:[~2013-06-06 15:17 UTC|newest]

Thread overview: 19+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2013-06-06 12:03 [Cluster-devel] [PATCH 1/4] mkfs.gfs2: Set sunit and swidth from probed io limits Andrew Price
2013-06-06 12:03 ` [Cluster-devel] [PATCH 2/4] mkfs.gfs2: Align resource groups to RAID stripes Andrew Price
2013-06-06 12:06   ` Steven Whitehouse
2013-06-06 12:19     ` Andrew Price
2013-06-06 12:57   ` Bob Peterson
2013-06-06 13:04     ` Andrew Price
2013-06-06 13:17       ` Bob Peterson
2013-06-06 13:11     ` Steven Whitehouse
2013-06-06 13:30       ` Bob Peterson
2013-06-06 15:17       ` Andrew Price [this message]
2013-06-06 12:03 ` [Cluster-devel] [PATCH 3/4] mkfs.gfs2: Create new resource groups on-demand Andrew Price
2013-06-06 13:07   ` Bob Peterson
2013-06-06 13:50     ` Andrew Price
2013-06-06 12:03 ` [Cluster-devel] [PATCH 4/4] mkfs.gfs2: Add align option and update docs Andrew Price
2013-06-06 12:15   ` Steven Whitehouse
2013-06-06 12:45     ` Andrew Price
2013-06-06 12:53       ` Steven Whitehouse
2013-06-06 13:13   ` Bob Peterson
2013-06-06 13:53     ` Andrew Price

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=51B0A81F.2010605@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 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).