linux-raid.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Mike Hardy <mhardy@h3c.com>
To: linux-raid@vger.kernel.org
Subject: Re: Fwd: Linux MD raid5 and reiser4... Any experience ?
Date: Fri, 06 Jan 2006 11:05:35 -0800	[thread overview]
Message-ID: <43BEBF7F.2060701@h3c.com> (raw)
In-Reply-To: <43BE3C99.4050706@ieee.org>


Slightly off-topic, but:

Simon Valiquette wrote:
> Francois Barre a écrit :


>   On production server with large RAID array, I tends to like very
> much XFS and trust it more than ReiserFS (I had some bad experience
> with ReiserFS in the past).  You can also grow a XFS filesystem live,
> which is really nice.

I didn't know this until recently, but ext2/3 can be grown online as
well (using 'ext2online'), given that you create it originally with
enough block group descriptor table room to support the size you're
growing too.

From the man page for mke2fs:

-E extended-options
       Set  extended options for the filesystem.  Extended options are
       comma separated, and may take  an  argument  using  the  equals
       (’=’) sign.  The -E option used to be -R in earlier versions of
       mke2fs.  The -R option is still accepted for backwards compati-
       bility.   The following extended options are supported:
             stride=stripe-size
                   Configure  the  filesystem  for  a  RAID array with
                   stripe-size filesystem blocks per stripe.

             resize=max-online-resize
                   Reserve  enough  space  so  that  the  block  group
                   descriptor  table  can grow to support a filesystem
                   that has max-online-resize blocks.

I have done it, and it works.

-Mike

-
To unsubscribe from this list: send the line "unsubscribe linux-raid" in
the body of a message to majordomo@vger.kernel.org
More majordomo info at  http://vger.kernel.org/majordomo-info.html

  parent reply	other threads:[~2006-01-06 19:05 UTC|newest]

Thread overview: 31+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <fd8d0180601050104x15079396h@mail.gmail.com>
2006-01-05  9:06 ` Fwd: Linux MD raid5 and reiser4... Any experience ? Francois Barre
2006-01-05 10:14   ` Daniel Pittman
2006-01-05 11:21     ` Francois Barre
2006-01-05 11:31       ` Gordon Henderson
2006-01-06  6:33       ` Daniel Pittman
2006-01-06  9:47       ` Simon Valiquette
2006-01-06 10:50         ` Francois Barre
2006-01-06 19:28           ` Forrest Taylor
2006-01-06 11:03         ` Kanotix crashed my raid PFC
2006-01-06 12:02           ` PFC
2006-01-06 12:08             ` PFC
2006-01-06 22:01               ` PFC
     [not found]                 ` <200601090803.03588.mlaks@verizon.net>
2006-01-09 18:30                   ` PFC
2006-01-06 19:05         ` Mike Hardy [this message]
2006-01-08  2:53         ` Fwd: Linux MD raid5 and reiser4... Any experience ? Daniel Pittman
2006-01-05 11:26     ` berk walker
2006-01-05 11:35       ` Francois Barre
2006-01-05 11:43         ` Gordon Henderson
2006-01-05 11:59         ` berk walker
2006-01-05 13:13         ` Bill Rugolsky Jr.
2006-01-05 13:38   ` John Stoffel
2006-01-05 14:03     ` Francois Barre
2006-01-05 18:55       ` John Stoffel
2006-01-06  9:08         ` Francois Barre
2006-01-06 10:49           ` Andre Majorel
2006-01-09  8:00             ` Molle Bestefich
2006-01-09  8:16               ` Gordon Henderson
2006-01-09  9:00                 ` Francois Barre
2006-01-09  9:24                   ` Molle Bestefich
2006-01-05 17:32 Andrew Burgess
2006-01-05 17:50 ` Francois Barre

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=43BEBF7F.2060701@h3c.com \
    --to=mhardy@h3c.com \
    --cc=linux-raid@vger.kernel.org \
    /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).