From: Shailendra Tripathi <stripathi@agami.com>
To: cousins@umit.maine.edu
Cc: xfs@oss.sgi.com
Subject: Re: swidth with mdadm and RAID6
Date: Tue, 19 Sep 2006 22:28:40 +0530 [thread overview]
Message-ID: <451021C0.8040701@agami.com> (raw)
In-Reply-To: <Pine.LNX.4.10.10609191233310.2460-100000@limpet.umeoce.maine.edu>
> Hi Shailendra,
>
> I ran the program and it reports:
>
> Level 6, disks=11 spare_disks=1 raid_disks=10
>
> which looks good. I don't understand why you got:
>
> Level 5, disks=7 spare_disks=3 raid_disks=5
>
> Why would it have 3 spare_disks?
Perhaps you are running more recent kernel than mine, and, spare_disks
now reports only actual spares. It did appear little weired that it
reported spare_disks as 3. get_array_info is changed in recent kernels
and that should explain this difference.
next prev parent reply other threads:[~2006-09-19 16:59 UTC|newest]
Thread overview: 19+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <fc.004c4d192b2da8e03b9aca0078918430.2b2da8e5@umit.maine.edu>
2006-09-19 16:36 ` swidth with mdadm and RAID6 Steve Cousins
2006-09-19 16:58 ` Shailendra Tripathi [this message]
2006-09-19 17:13 ` Steve Cousins
[not found] <fc.004c4d192b3470d73b9aca0029fcf469.2b349301@umit.maine.edu>
2006-09-19 17:52 ` Steve Cousins
2006-09-19 19:22 ` Steve Cousins
2006-09-19 20:19 ` Shailendra Tripathi
[not found] <fc.004c4d192b2c45a93b9aca00fc3f0f38.2b2c4b4d@umit.maine.edu>
2006-09-18 20:28 ` Steve Cousins
2006-09-18 20:44 ` Steve Cousins
2006-09-18 21:06 ` Shailendra Tripathi
2006-09-18 22:13 ` Shailendra Tripathi
2006-09-19 5:11 ` Timothy Shimmin
2006-09-19 6:44 ` Shailendra Tripathi
2006-09-19 7:02 ` Timothy Shimmin
[not found] <fc.004c4d192b2a17d13b9aca00b4f73745.2b2a26d7@umit.maine.edu>
2006-09-18 15:33 ` Steve Cousins
2006-09-18 18:10 ` Shailendra Tripathi
2006-09-18 18:19 ` Shailendra Tripathi
2006-09-15 21:07 Steve Cousins
2006-09-15 23:49 ` Peter Grandi
2006-09-18 14:50 ` Shailendra Tripathi
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=451021C0.8040701@agami.com \
--to=stripathi@agami.com \
--cc=cousins@umit.maine.edu \
--cc=xfs@oss.sgi.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