From: Bob Peterson <rpeterso@redhat.com>
To: cluster-devel.redhat.com
Subject: [Cluster-devel] [PATCH 2/4] mkfs.gfs2: Align resource groups to RAID stripes
Date: Thu, 6 Jun 2013 09:17:15 -0400 (EDT) [thread overview]
Message-ID: <1439287716.48101227.1370524635435.JavaMail.root@redhat.com> (raw)
In-Reply-To: <51B088C2.4080701@redhat.com>
| > In GFS1, we allowed mix-and-match resource group sizes, but we originally
| > Do we still want to enforce this rule?
|
| Good question. I had assumed that we don't have a rule like that as the
| rindex specifies the rg sizes. My next planned mkfs change is to allow
| the journal creation code to ask for a resource group large enough to
| contain all of a journal's data blocks so that they're always a single
| extent. Returning to enforcing the rule would have implications for that
| plan, too.
|
| Andy
Hi,
Some more thoughts to add to this discussion:
First, since we're now trying to align our rgrps to raid stripes, maybe
the rules no longer make sense.
Second, we probably want to change gfs2_grow to ensure that new rgrps
are also placed on the same stripe boundaries. If we enforce the uniform
rgrp rule, this would probably happen automatically. If we don't, I bet
gfs2_grow would need to change.
Bob Peterson
Red Hat File Systems
next prev parent reply other threads:[~2013-06-06 13: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 [this message]
2013-06-06 13:11 ` Steven Whitehouse
2013-06-06 13:30 ` Bob Peterson
2013-06-06 15:17 ` Andrew Price
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=1439287716.48101227.1370524635435.JavaMail.root@redhat.com \
--to=rpeterso@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).