From: Ming Zhang <mingz@ele.uri.edu>
To: Brad Campbell <brad@wasp.net.au>
Cc: Linux RAID <linux-raid@vger.kernel.org>
Subject: Re: skip raid5 reconstruction
Date: Fri, 08 Jul 2005 08:22:46 -0400 [thread overview]
Message-ID: <1120825366.5461.14.camel@localhost.localdomain> (raw)
In-Reply-To: <42CB7E65.5010204@wasp.net.au>
On Wed, 2005-07-06 at 10:47 +0400, Brad Campbell wrote:
> Ming Zhang wrote:
> > Hi folks
> >
> > I am testing some HW performance with raid5 with 2.4.x kenrel.
> >
> > It is really troublesome every time I create a raid5, wait 4 hours for
> > reconstruction, and then test some data and then recreate another one
> > and wait again. I wonder if there is any hack or option available to
> > create a raid5 without reconstruct the parity disk. I just have interest
> > to test the performance so do not care about data correctness at this
> > stage.
>
> I did a similar thing a while back.
> I created the raid and waited for it to sync, I then make dd copies of the raid superblocks.
> When I blew it up I just dd the clean superblocks back again (saved a 12 hour rebuild time)
interesting to know about this. u just check the dmesg and see where is
the sb and then u dd it out and dd back later?
>
> Having just thought about what you wrote, I guess you are building the raid in different
> configurationes each time, so my method might not be good for you.
>
yes, i changed it many times.
thx anyway!
Ming
> Regards,
> Brad
next prev parent reply other threads:[~2005-07-08 12:22 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2005-07-05 17:22 skip raid5 reconstruction Ming Zhang
2005-07-06 6:47 ` Brad Campbell
2005-07-08 12:22 ` Ming Zhang [this message]
2005-07-08 18:14 ` Brad Campbell
2005-07-08 19:25 ` Ming Zhang
2005-07-06 15:45 ` Michael Tokarev
2005-07-06 15:47 ` Ming Zhang
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=1120825366.5461.14.camel@localhost.localdomain \
--to=mingz@ele.uri.edu \
--cc=brad@wasp.net.au \
--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.