From: "Ty! Boyack" <ty@nrel.colostate.edu>
To: linux-raid@vger.kernel.org
Subject: Re: managing raid on linux
Date: Wed, 23 Apr 2008 09:55:18 -0600 [thread overview]
Message-ID: <480F5BE6.7070908@nrel.colostate.edu> (raw)
In-Reply-To: <480F4EF6.1000103@tmr.com>
I'm not quite "hardware flavor of the month" but I still feel like I've
got all 31 flavors around the shop.
Something you might look into is SMI-S (Storage Management Initiative -
Specification), which is being promoted by SNIA (Storage Network
Industry Association):
http://www.snia.org/tech_activities/standards/curr_standards/smi/
The goal is to provide a single management protocol/API for any
traditional storage hardware (including arrays, switches, NAS devices,
tape libraies, etc.). As I understand it, there are hooks for the
standard operations and monitoring, and extensibility for specialized
devices.
While it has been targeted at SAN hardware, it would seem that the array
management features could be used on their own in your case, if your
arrays support this. There are some open source projects working on
providing a management tool for these devices. It's been on my horizon
for a while, but I have not had the chance to really look into it from a
practical sense. So I don't know if it is exactly what you might need,
but it could be worth exploring.
(I know it's WAY outside of the kernel space tools you mentioned, but it
is a mature option)
-Ty!
Bill Davidsen wrote:
> devzero@web.de wrote:
>> Hello !
>>
>> since we use lots of servers with raid where i work, for every system
>> i need to go trough that hassle to find out, how to monitor the state
>> of the raid array.
>>
>> if you you have more than one brand of raid controller, you really
>> need a large amount of time to find the proper tool for this, if you
>> think you found it, then you have a broken link or the wrong version,
>> the tool is outdated, doesn`t work with recent controller versions,
>> is tricky to setup or difficult to use.
>>
>> this takes a lot of time and is a major annoyance.
>>
>> isn`t there a linux project which is adressing this?
>> some site for the sysadmin to consult?
>> i have raid controller xyz, what do i need to monitor the arrays
>> state....?
>>
>> i would expect, that the linux kernel would provide sort of a
>> standardized way to check the health state of a raid array - i.e.
>> this should be completely done in kernel space, as some raid drivers do.
>>
>> instead i need to use a dozen different tools, which are often closed
>> source, too.
>>
>> anybody suffer from that headaches, too ?
>>
>
> You have that option, set your controllers to JBOD and use software
> raid. Most people don't play "flavor of the month" with hardware, and
> those of us who let purchasing alter hardware specs to "save money"
> use software raid.
>
--
-===========================-
Ty! Boyack
NREL Unix Network Manager
ty@nrel.colostate.edu
(970) 491-1186
-===========================-
next prev parent reply other threads:[~2008-04-23 15:55 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-04-20 21:51 managing raid on linux devzero
2008-04-23 15:00 ` Bill Davidsen
2008-04-23 15:55 ` Ty! Boyack [this message]
2008-04-23 18:17 ` managing raid on Linux David Lethe
[not found] ` <20080423184722.GA4889@rap.rap.dk>
2008-04-23 19:21 ` David Lethe
2008-04-26 19:39 ` Bill Davidsen
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=480F5BE6.7070908@nrel.colostate.edu \
--to=ty@nrel.colostate.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).