From: Max Waterman <davidmaxwaterman+news@fastmail.co.uk>
To: linux-raid@vger.kernel.org
Subject: Re: raidreconfig advice
Date: Thu, 28 Jul 2005 10:28:05 +0800 [thread overview]
Message-ID: <dc9fsa$r94$1@sea.gmane.org> (raw)
In-Reply-To: <42331AC6.6050109@h3c.com>
Mike Hardy wrote:
>
>
> Max Waterman wrote:
>
>> OK, I am going to try to expand the capacity of my raid5 array and I
>> want to make sure I've got it right.
>
>
> Not a bad idea, as its all or nothing...
>
>> Disk /dev/hdg: 200.0 GB, 200049647616 bytes
>> Disk /dev/hdi: 200.0 GB, 200049647616 bytes
>> Disk /dev/hdk: 200.0 GB, 200049647616 bytes
>> Disk /dev/sda: 200.0 GB, 200049647616 bytes
>> Disk /dev/sdb: 200.0 GB, 200049647616 bytes
>> Disk /dev/sdc: 200.0 GB, 200049647616 bytes
>> Disk /dev/sdd: 200.0 GB, 200049647616 bytes
>
>
> They certainly all looked the same (including the C/H/S counts)
>
>> This leaves me with sdc which I can try to add. If that goes OK, I'll
>> trash the backup and add sd[ab] too.
>
>
> I'd be very wary of this, for two reasons. One, you have the backup
> during the add for a reason. If anything goes wrong, there goes your
> data. Second, where would you ever back your raid up to? What about fs
> corruption?
>
> The rule of thumb with databases is to always have enough contiguous
> scratch space to dump and restore your biggest table. With large RAID,
> you should always be able to dump and restore your largest raid device,
> imho. Its a bunch more disk yes, but you'll need it at some point, I
> promise. Many future tears can be averted...
I'm not worried about losing my data enough to make regular backups.
I recently thought I'd lost all my data - it wasn't that much of a
shock. I since discovered I hadn't lost it all, so all is well.
I've made a backup onto a spare array, plus onto one of the 200GB disks
which I will use as a spare later.
>
>> 3) Are there any instructions for raidreconfig? I understand is uses
>> some non-mdadm config files as from/to input.
>
>
> the man page is great - honest. Two conf files (current and future) and
> you're set
Yeah, but I don't know how to use raidconf files. I use mdadm. I
currently have in my mdadm.conf :
DEVICE /dev/hd[egik]
ARRAY /dev/md0 level=raid5 num-devices=4 devices=/dev/hd[egik]
I think my target mdadm.conf would be :
DEVICE /dev/hd[egik] /dev/sd[abc]
ARRAY /dev/md0 level=raid5 num-devices=7
devices=/dev/hd[egik],/dev/sd[abc]
What are these in raidtab(5) terms?
Max.
prev parent reply other threads:[~2005-07-28 2:28 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2005-03-12 9:21 raidreconfig advice Max Waterman
2005-03-12 11:41 ` David Greaves
2005-03-12 13:26 ` raidreconf advice Max Waterman
2005-03-12 16:37 ` raidreconfig advice Mike Hardy
2005-07-28 2:28 ` Max Waterman [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='dc9fsa$r94$1@sea.gmane.org' \
--to=davidmaxwaterman+news@fastmail.co.uk \
--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).