From: "Jonathan Vardy" <jonathanv@explainerdc.com>
To: Andy Arvai <arvai@scripps.edu>, linux-raid@vger.kernel.org
Cc: linux-kernel@vger.kernel.org
Subject: Re: RAID 5 performance problems
Date: Thu, 3 Apr 2003 23:10:37 +0200 [thread overview]
Message-ID: <004901c2fa25$795b5d80$2e77c23e@pentium4> (raw)
In-Reply-To: 200304031949.LAA28555@astra.scripps.edu
you're right, it should be. When I was writing the original mail I had it
running in degraded mode so I edited the values that /proc/mdstat gave me to
match the array in normal mode. I forgot to make [_UUUU] [UUUUU]. I'm
currently rebuilding the array but it's taking some time...
md0 : active raid5 hdc1[5] hdk1[4] hdi1[3] hdg1[2] hde1[1]
468872704 blocks level 5, 128k chunk, algorithm 0 [5/4] [_UUUU]
[================>....] recovery = 83.1% (97429504/117218176)
finish=65.5min speed=5034K/sec
----- Original Message -----
From: "Andy Arvai" <arvai@scripps.edu>
To: <linux-raid@vger.kernel.org>
Cc: <linux-kernel@vger.kernel.org>
Sent: Thursday, April 03, 2003 9:49 PM
Subject: Re: RAID 5 performance problems
>
> Shouldn't /proc/mdstat have [UUUUU] instead of [_UUUU]? Perhaps
> this is running in degraded mode. Also, you have 'algorithm 0',
> whereas my raid5 has 'algorithm 2', which is the left-symmetric
> parity algorithm.
>
> Andy
>
> > cat /proc/mdstat gives:
> >
> > Personalities : [raid0] [raid5]
> > read_ahead 1024 sectors
> > md0 : active raid5 hdk1[4] hdi1[3] hdg1[2] hde1[1] hdc1[0]
> > 468872704 blocks level 5, 128k chunk, algorithm 0 [5/5] [_UUUU]
> > unused devices: <none>
>
>
>
> -
> 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
>
WARNING: multiple messages have this Message-ID (diff)
From: "Jonathan Vardy" <jonathanv@explainerdc.com>
To: "Andy Arvai" <arvai@scripps.edu>, <linux-raid@vger.kernel.org>
Cc: <linux-kernel@vger.kernel.org>
Subject: Re: RAID 5 performance problems
Date: Thu, 3 Apr 2003 23:10:37 +0200 [thread overview]
Message-ID: <004901c2fa25$795b5d80$2e77c23e@pentium4> (raw)
In-Reply-To: 200304031949.LAA28555@astra.scripps.edu
you're right, it should be. When I was writing the original mail I had it
running in degraded mode so I edited the values that /proc/mdstat gave me to
match the array in normal mode. I forgot to make [_UUUU] [UUUUU]. I'm
currently rebuilding the array but it's taking some time...
md0 : active raid5 hdc1[5] hdk1[4] hdi1[3] hdg1[2] hde1[1]
468872704 blocks level 5, 128k chunk, algorithm 0 [5/4] [_UUUU]
[================>....] recovery = 83.1% (97429504/117218176)
finish=65.5min speed=5034K/sec
----- Original Message -----
From: "Andy Arvai" <arvai@scripps.edu>
To: <linux-raid@vger.kernel.org>
Cc: <linux-kernel@vger.kernel.org>
Sent: Thursday, April 03, 2003 9:49 PM
Subject: Re: RAID 5 performance problems
>
> Shouldn't /proc/mdstat have [UUUUU] instead of [_UUUU]? Perhaps
> this is running in degraded mode. Also, you have 'algorithm 0',
> whereas my raid5 has 'algorithm 2', which is the left-symmetric
> parity algorithm.
>
> Andy
>
> > cat /proc/mdstat gives:
> >
> > Personalities : [raid0] [raid5]
> > read_ahead 1024 sectors
> > md0 : active raid5 hdk1[4] hdi1[3] hdg1[2] hde1[1] hdc1[0]
> > 468872704 blocks level 5, 128k chunk, algorithm 0 [5/5] [_UUUU]
> > unused devices: <none>
>
>
>
> -
> 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:[~2003-04-03 21:10 UTC|newest]
Thread overview: 43+ messages / expand[flat|nested] mbox.gz Atom feed top
2003-04-03 19:49 RAID 5 performance problems Andy Arvai
2003-04-03 20:25 ` Mike Dresser
2003-04-03 20:25 ` Mike Dresser
2003-04-03 21:10 ` Jonathan Vardy [this message]
2003-04-03 21:10 ` Jonathan Vardy
2003-04-03 21:31 ` Ezra Nugroho
-- strict thread matches above, loose matches on Subject: below --
2003-04-04 16:01 Jonathan Vardy
2003-04-04 16:01 ` Jonathan Vardy
2003-04-05 0:10 ` Jonathan Vardy
2003-04-05 0:10 ` Jonathan Vardy
2003-04-04 15:05 Jonathan Vardy
2003-04-04 15:05 ` Jonathan Vardy
2003-04-04 11:44 Jonathan Vardy
2003-04-04 11:44 ` Jonathan Vardy
2003-04-04 14:39 ` Ezra Nugroho
2003-04-03 20:10 Chuck Ebbert
2003-04-03 19:13 Neil Schemenauer
2003-04-03 15:45 Jonathan Vardy
2003-04-03 15:45 ` Jonathan Vardy
2003-04-03 18:05 ` Peter L. Ashford
2003-04-03 18:05 ` Peter L. Ashford
2003-04-03 18:47 ` Ross Vandegrift
2003-04-03 19:22 ` Stephan van Hienen
2003-04-03 19:20 ` Stephan van Hienen
2003-04-03 19:28 ` Alan Cox
2003-04-03 21:02 ` Ezra Nugroho
2003-04-03 21:25 ` Stephan van Hienen
2003-04-03 21:38 ` Peter L. Ashford
2003-04-03 21:38 ` Peter L. Ashford
2003-04-03 22:09 ` Jonathan Vardy
2003-04-03 22:09 ` Jonathan Vardy
2003-04-03 22:16 ` Jonathan Vardy
2003-04-03 22:16 ` Jonathan Vardy
2003-04-03 22:28 ` Peter L. Ashford
2003-04-03 22:28 ` Peter L. Ashford
2003-04-03 21:42 ` Jonathan Vardy
2003-04-03 21:42 ` Jonathan Vardy
2003-04-03 22:13 ` Peter L. Ashford
2003-04-03 22:13 ` Peter L. Ashford
2003-04-04 20:39 ` H. Peter Anvin
2003-04-03 21:06 ` Felipe Alfaro Solana
2003-04-03 21:14 ` Jonathan Vardy
2003-04-03 21:14 ` Jonathan Vardy
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='004901c2fa25$795b5d80$2e77c23e@pentium4' \
--to=jonathanv@explainerdc.com \
--cc=arvai@scripps.edu \
--cc=linux-kernel@vger.kernel.org \
--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.