From: Fabien Salvi <fabien@cri74.org>
To: Lester Hightower <hightowe@10east.com>
Cc: "'linux-scsi@vger.kernel.org'" <linux-scsi@vger.kernel.org>
Subject: Re: [FEATURE REQUEST] megaraid2 driver
Date: Thu, 22 Apr 2004 12:11:18 +0200 [thread overview]
Message-ID: <40879A46.4090603@cri74.org> (raw)
In-Reply-To: <Pine.LNX.4.58.0404210952220.29661@les5.10east.com>
Lester Hightower a écrit :
> Atul / readers of linux-scsi,
> [...]
> Yesterday we ran a test where we pulled a drive from a logical drive set
> that had a hot spare. The MegaRaid card rebuilt automatically, and after
> we inserted a fresh disk it automatically marked as a hot spare. That
> went well, however, it took almost two hours to rebuild 73G on u320 disks
> in raid-1, which surprised me since the Mylex Acceleraid 170 (u160) took
> less than an hour in the same test.
Well, not very surprising. Speed can vary from one manufacturer to another.
It also depends of the priority given to this task...
> One thing the DAC960 driver does is publish the real-time progress of a
> rebuild operation, both in /proc and by klog every few minutes. The Linux
> MegaRaid driver is completely silent start to finish, only showing that it
> is in a Rebuild state. Because the DAC960 card had already given us an
> idea of how much time to expect the rebuild to take, the second hour that
> the MegaRaid consumed was unnerving, and primarily due to the fact that we
> had no rebuild progress indication available to us.
It's not the driver's job to display this...
> I searched through all of the structs in megariad2.h and do not readily
> see any data available that would indicate the progress of a rebuild, else
> I would code this myself and submit a patch. Instead I am asking Atul,
> and anyone else with expertise in this area, for assistance or advice in
> implementing that feature.
You should look at userland utilities to manager your RAID controller.
I've not tested them with megaraid2 driver, but you should look at
LSILogic support web site to get utilities (GAM, Megamgr, etc...).
--
Fabien SALVI
-
To unsubscribe from this list: send the line "unsubscribe linux-scsi" 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:[~2004-04-22 10:11 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-04-09 5:11 [ANNOUNCE]: megaraid driver version 2.10.3 Mukker, Atul
2004-04-16 12:06 ` 'Christoph Hellwig'
2004-04-21 14:09 ` [FEATURE REQUEST] megaraid2 driver Lester Hightower
2004-04-22 10:11 ` Fabien Salvi [this message]
-- strict thread matches above, loose matches on Subject: below --
2004-04-22 13:47 Mukker, Atul
2004-04-22 13:56 ` Lester Hightower
2004-04-22 13:59 Mukker, Atul
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=40879A46.4090603@cri74.org \
--to=fabien@cri74.org \
--cc=hightowe@10east.com \
--cc=linux-scsi@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