linux-raid.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Ming Zhang <mingz@ele.uri.edu>
To: Linux RAID <linux-raid@vger.kernel.org>
Subject: skip raid5 reconstruction
Date: Tue, 05 Jul 2005 13:22:47 -0400	[thread overview]
Message-ID: <1120584167.5535.56.camel@localhost.localdomain> (raw)

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.

Thanks!


Ming





             reply	other threads:[~2005-07-05 17:22 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2005-07-05 17:22 Ming Zhang [this message]
2005-07-06  6:47 ` skip raid5 reconstruction Brad Campbell
2005-07-08 12:22   ` Ming Zhang
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=1120584167.5535.56.camel@localhost.localdomain \
    --to=mingz@ele.uri.edu \
    --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).