From: Mads Peter Bach <mpb@hum.auc.dk>
To: linux-raid@vger.kernel.org
Subject: Re: Converting existing Data to RAID5
Date: Fri, 02 May 2003 19:46:13 +0200 [thread overview]
Message-ID: <3EB2AEE5.10803@hum.auc.dk> (raw)
In-Reply-To: <20030502172613.GA20267@moof.org.uk>
Giles A. Radford wrote:
> Now, Having read back on this list the stock answer to "I want to
> expand my RAID5 array" seems to be (at the moment) "Use raidreconf,
> but at your own risk, and it'll take ages". I don't have a problem with
> the "ages" bit, but I'd like to be as datasafe as possible.
> Could I start up a Raid 5 array with one or two real disks and three
> or four faulty drives which I would then activate as and when copying
> from them onto the new array has finished?
No, sorry, that wouldn't work. You can have one one drive missing. raidreconf
is probably your best bet.
> On a slightly similar note, I'm used to using ext2 and ext3, but I've
> heard a lot of people talk positively about XFS recently, so I'm
> wondering if any of you have any opinions on whether I should use ext3
> or XFS for this new array?
Depends on your application. I quite fond of XFS in my fileservers, but it has
the added hassle of requiring patches to the standard kernel, unless you use a
distro with XFS support, but they tend to lag a bit behind.
--
Mads Peter Bach
Systemadministrator, Det Humanistiske Fakultet, Aalborg Universitet
Kroghstræde 3 - 5.111, DK-9220 Aalborg Øst - (+45) 96358062
# whois MPB1-DK@whois.dk-hostmaster.dk
-
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
prev parent reply other threads:[~2003-05-02 17:46 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2003-05-02 17:26 Converting existing Data to RAID5 Giles A. Radford
2003-05-02 17:46 ` Mads Peter Bach [this message]
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=3EB2AEE5.10803@hum.auc.dk \
--to=mpb@hum.auc.dk \
--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 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.