From: berk walker <berk@panix.com>
To: Mike Hardy <mhardy@h3c.com>
Cc: Frank Wittig <fw@weisshuhn.de>,
John Poirier <john.poirier@case.edu>,
linux-raid@vger.kernel.org
Subject: Re: md Grow for Raid 5
Date: Tue, 08 Mar 2005 18:14:59 -0500 [thread overview]
Message-ID: <422E31F3.3070104@panix.com> (raw)
In-Reply-To: <422E1C6A.2000006@h3c.com>
Have you guys seen/tried mdadm 1.90? I am delightfully experiencing the
neat issues [read problems] with MY system [sys1], and am too into
myself to be able to take on serious other-probs. The doc [which is
still a tad lite, NB] has a grow command. Understand that your files
exist on/in a filesystem, which has a _size_. Growing RAID and growing
fs are two, nonrelated things. But if you want #2, then you have to do
both 1 & 2. There is definately more than one way to "skin a cat", so
pgms of which you are familiar might be queried first.
Price - 2cents
b-
caveat:
You may not get what you paid for -
but, you always pay for what you get. <-Practise .sig
Mike Hardy wrote:
>
> Frank Wittig wrote:
>
>> It actually is available.
>> I've tested it and it worked fine for me. But taking a backup is
>> highly recommended.
>> The trick is not to use mdadm, since growing with mdadm is not
>> possible at the moment. Use raid-tools instead.
>> The program raidreconf comes along with raidtools. This prog takes
>> two raid-tab files as input which describe the array configuration
>> before and after reconfiguration. (See man raidreconf for further
>> details)
>
>
> I'll second both major points here:
>
> raidreconf does work, but it can fail and leave things completely
> destroyed (imagine one bad block somewhere after parity was partially
> migrated), so take a backup.
>
> Given that you're taking a backup already then, creating a new array
> (with its optimized resync) might be faster if its an online backup.
>
> I'm 2 for 4 now on raidreconf working, with the two failures (sadly)
> being of the "operator error" variety - raidreconf is picky and fails
> slow if your disk sizes aren't what it expects, I found. It got to the
> end and ran out of space on me due to a slightly different "250GB"
> disk size once. The other was a bad block along the way - I should
> have done smartctl -t long on all drives prior to resize. Both lessons
> learned...
>
> -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
>
> .
>
next prev parent reply other threads:[~2005-03-08 23:14 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2005-03-08 18:23 md Grow for Raid 5 John Poirier
2005-03-08 19:34 ` Frank Wittig
2005-03-08 21:43 ` Mike Hardy
2005-03-08 23:14 ` berk walker [this message]
2005-03-08 23:20 ` Mike Hardy
2005-03-08 23:55 ` Neil Brown
2005-03-10 12:10 ` David Greaves
2005-03-09 9:31 ` Frank Wittig
2005-03-08 22:57 ` berk walker
2005-03-08 23:15 ` Mike Tran
2005-03-08 23:35 ` berk walker
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=422E31F3.3070104@panix.com \
--to=berk@panix.com \
--cc=fw@weisshuhn.de \
--cc=john.poirier@case.edu \
--cc=linux-raid@vger.kernel.org \
--cc=mhardy@h3c.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 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).