From: "TJ Harrell" <systemloc@earthlink.net>
To: linux-raid@vger.kernel.org
Subject: Re: Add disks to RAID5 array
Date: Thu, 22 Jul 2004 14:33:09 -0400 [thread overview]
Message-ID: <002f01c4701a$5712b180$0201a8c0@windows> (raw)
In-Reply-To: 200407221807.i6MI7S328145@watkins-home.com
I've used raidreconf to convert from RAID 1 to RAID 5 and to grow RAID 5
arrays. I would recommend a UPS. If the power blips, the array will be lost.
Other then that, I've never had any trouble whatsoever with it. IMO,
resize2fs is more dangerous than using raidreconf. I have had resize2fs
corrupt file systems badly before. It's important to run fsck -f both before
and after resize2fs. It catches a lot of minor, fixable problems after the
resize2fs is run. Doing this, I have successfully grown RAID 5 arrays many
times without any trouble.
In any case, backing up is highly recommended if you value the data!
----- Original Message -----
From: "Guy" <bugzilla@watkins-home.com>
To: <robin-lists@robinbowes.com>; <linux-raid@vger.kernel.org>
Sent: Thursday, July 22, 2004 2:07 PM
Subject: RE: Add disks to RAID5 array
> A tool called Raidreconf can do what you want.
> I have never used it.
> I don't know how much risk there is in data loss.
> I would backup my data first!
>
> Find it, read about it, and understand it.
>
> Maybe someone else can comment on the risks?
>
> Guy
next prev parent reply other threads:[~2004-07-22 18:33 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-07-22 16:20 Add disks to RAID5 array robin-lists
2004-07-22 17:59 ` TJ Harrell
2004-07-22 18:07 ` Guy
2004-07-22 18:33 ` TJ Harrell [this message]
2004-07-22 18:51 ` Robin Bowes
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='002f01c4701a$5712b180$0201a8c0@windows' \
--to=systemloc@earthlink.net \
--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.