All of lore.kernel.org
 help / color / mirror / Atom feed
From: Michael Monnerie <michael.monnerie@is.it-management.at>
To: xfs@oss.sgi.com
Subject: Re: xfs mount/create options (was: XFS status update for August 2010)
Date: Thu, 9 Sep 2010 01:30:15 +0200	[thread overview]
Message-ID: <201009090130.22983@zmi.at> (raw)
In-Reply-To: <20100908145148.GB705@dastard>


[-- Attachment #1.1: Type: Text/Plain, Size: 1190 bytes --]

On Mittwoch, 8. September 2010 Dave Chinner wrote:
> Dynamically changing the RAID array geometry is a Bad Idea.  Yes,
> you can do it, but if you've got a filesystem full of data and
> metadata aligned to the old geometry then after the modification
> it won't be aligned anymore.
> 
> If you want to do this, then either don't bother about geomtry hints
> in the first place, or dump, rebuild the array, mkfs and restore so
> everything is properly aligned with the new world order. Hell,
> dump/mkfs/restore might even be faster than reshaping a large
> array...
 
You're right. But there are some customers who don't want to spend the 
money for a 2nd array, and can't afford the downtime of backup, rebuild 
raid (takes 8-48 hours), restore. So an online upgrade is needed. We're 
not in an ideal world.

-- 
mit freundlichen Grüssen,
Michael Monnerie, Ing. BSc

it-management Internet Services
http://proteger.at [gesprochen: Prot-e-schee]
Tel: 0660 / 415 65 31

****** Aktuelles Radiointerview! ******
http://www.it-podcast.at/aktuelle-sendung.html

// Wir haben im Moment zwei Häuser zu verkaufen:
// http://zmi.at/langegg/
// http://zmi.at/haus2009/

[-- 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

  parent reply	other threads:[~2010-09-08 23:29 UTC|newest]

Thread overview: 24+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2010-09-02 14:59 XFS status update for August 2010 Christoph Hellwig
2010-09-02 14:59 ` Christoph Hellwig
2010-09-05  7:44 ` Willy Tarreau
2010-09-05  7:44   ` Willy Tarreau
2010-09-05  9:37   ` Michael Monnerie
2010-09-05 10:47     ` Willy Tarreau
2010-09-05 13:08       ` Dave Chinner
2010-09-05 18:56         ` Willy Tarreau
2010-09-05 23:36           ` Dave Chinner
2010-09-06  5:19             ` Willy Tarreau
2010-09-06  5:49         ` xfs mount/create options (was: XFS status update for August 2010) Michael Monnerie
2010-09-08  5:38           ` Michael Monnerie
2010-09-08 10:58             ` Dave Chinner
2010-09-08 13:38               ` Michael Monnerie
2010-09-08 14:51                 ` Dave Chinner
2010-09-08 15:24                   ` Emmanuel Florac
2010-09-08 23:34                     ` Michael Monnerie
2010-09-08 23:30                   ` Michael Monnerie [this message]
2010-09-09  7:27                     ` Dave Chinner
2010-09-09  8:29                       ` Michael Monnerie
2010-09-06  3:22     ` XFS status update for August 2010 Eric Sandeen
2010-09-06  5:10       ` Michael Monnerie
2010-09-06 22:55 xfs mount/create options (was: XFS status update for August 2010) Richard Scobie
2010-09-06 23:31 ` Michael Monnerie

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=201009090130.22983@zmi.at \
    --to=michael.monnerie@is.it-management.at \
    --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 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.