From: Michael Monnerie <michael.monnerie@is.it-management.at>
To: xfs@oss.sgi.com, stan@hardwarefreak.com
Subject: Re: Optimal XFS formatting options?
Date: Tue, 17 Jan 2012 10:19:55 +0100 [thread overview]
Message-ID: <201201171019.58714@zmi.at> (raw)
In-Reply-To: <4F14EBAF.10808@hardwarefreak.com>
[-- Attachment #1.1: Type: Text/Plain, Size: 1379 bytes --]
On Dienstag, 17. Januar 2012 Stan Hoeppner wrote:
> Thanks for the correction/reminder Dave. So in this case the first
> sector of the first partition would need to reside at LBA1280 in this
> array (655360 byte stripe width, 1280 sectors/stripe), as the
> partition table itself is going to occupy some sectors at the
> beginning of the first stripe. By creating the partition at LBA1280
> we make sure the first sector of the XFS filesystem is aligned with
> the first sector of the 2nd stripe.
There's one big problem with that: Many people will sooner or later
expand and existing array. If you add one drive, all your nice stripe
width alignment becomes bogus, and suddenly your performance will drop.
There's no real way out of that, but three solutions come to my mind:
- backup before expand/restore after expand with new alignment
- leave existing data, just change mount options so after expansion at
least new files are going to be aligned to the new stripe width.
- expand array by factors of two. So if you have 10 data drives, add 10
data drives. But that creates other problems (probability of single
drive failure + time to recover a single broken disk)
--
mit freundlichen Grüssen,
Michael Monnerie, Ing. BSc
it-management Internet Services: Protéger
http://proteger.at [gesprochen: Prot-e-schee]
Tel: +43 660 / 415 6531
[-- Attachment #1.2: This is a digitally signed message part. --]
[-- Type: application/pgp-signature, Size: 198 bytes --]
[-- Attachment #2: Type: text/plain, Size: 121 bytes --]
_______________________________________________
xfs mailing list
xfs@oss.sgi.com
http://oss.sgi.com/mailman/listinfo/xfs
next prev parent reply other threads:[~2012-01-17 9:20 UTC|newest]
Thread overview: 17+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-01-14 17:44 Optimal XFS formatting options? MikeJeezy
2012-01-14 22:23 ` Stan Hoeppner
2012-01-16 0:27 ` MikeJeezy
2012-01-16 4:56 ` Stan Hoeppner
2012-01-16 23:11 ` Dave Chinner
2012-01-17 3:31 ` Stan Hoeppner
2012-01-17 9:19 ` Michael Monnerie [this message]
2012-01-17 11:17 ` Emmanuel Florac
2012-01-17 11:34 ` Stan Hoeppner
2012-01-20 15:52 ` Michael Monnerie
2012-01-20 22:44 ` Stan Hoeppner
2012-01-24 10:31 ` Michael Monnerie
2012-01-15 1:14 ` Peter Grandi
2012-01-20 9:03 ` Linda Walsh
2012-01-20 12:06 ` Peter Grandi
2012-01-20 15:55 ` Michael Monnerie
2012-01-23 4:21 ` Dave Chinner
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=201201171019.58714@zmi.at \
--to=michael.monnerie@is.it-management.at \
--cc=stan@hardwarefreak.com \
--cc=xfs@oss.sgi.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