From: berk walker <berk@panix.com>
To: Mike Tran <mhtran@us.ibm.com>
Cc: linux-raid@vger.kernel.org
Subject: Re: md Grow for Raid 5
Date: Tue, 08 Mar 2005 18:35:13 -0500 [thread overview]
Message-ID: <422E36B1.1020609@panix.com> (raw)
In-Reply-To: <422E31FC.7070104@us.ibm.com>
Mike, check him out, google him. Man is really open, good/talanted, and
the author of mdadm.
That being said, the dox for it do seem a bit lean, but at least give
it/him a look, ok?
And on other tools, google on that, also. Google is the compuweenies
friend - *usually* works for me. [if you need help on whatis google,
etc, priv. mail me]
b-
Mike Tran wrote:
> How does mdadm grow a raid5 array?
> Could you please provide an URL to other tools which can perform
> online capacity expansion of md raid5 arrays?
>
> --
> Regards,
> Mike T.
>
> berk walker wrote:
>
>>
>>
>> Already are, John. mdadm, and two or three others.
>> b-
>> John Poirier wrote:
>>
>>> Greets,
>>
>>
>>
>>
>>> A lot of RAID 5 hardware controllers can grow a RAID 5 array (online
>>> capacity expansion). Will this be available in software RAID?
>>>
>>> John
>>>
>>> -
>>
>>
>
>
> -
> 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:[~2005-03-08 23:35 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
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 [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=422E36B1.1020609@panix.com \
--to=berk@panix.com \
--cc=linux-raid@vger.kernel.org \
--cc=mhtran@us.ibm.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).