From: Frank Wittig <fw@weisshuhn.de>
To: rv@eychenne.org
Cc: linux-raid@vger.kernel.org
Subject: Re: Questions about software RAID
Date: Tue, 19 Apr 2005 21:46:56 +0200 [thread overview]
Message-ID: <42656030.6000506@weisshuhn.de> (raw)
In-Reply-To: <20050419175407.GK3103@eychenne.org>
Hervé Eychenne wrote:
>Maybe you are an experienced guy so it seems so simple to you... but
>I'm always amused when an experienced guy refuses to make things
>simpler for those who aren't as much as he is. And sends them to
>Microsoft. Great.
>
>
i don't send you to microsoft. i want you to understand the philosophy
behind linux.
the sort of functionality you want doesn't belong to the mdadm tool.
mdadm is the command line interface to dm.
more complex functionality like the one you desire is covered by
frontends like EVMS.
i don't know EVMS but what i heard about it sounds exactly like what you
want. simple administration without having to know how things work in
the background.
>I personnaly do not consider that this is yet another case. For me,
>RAID is about have disk availability, right? So the most common
>production case is definitely when one of your disks crashed, and you
>want to replace it.
>There must be some kind of way to deal with that without typing too
>much contextual command lines.
>
>
after the first time you lose data because of a failure of an automated
process you will think different about that.
i think automation is fine for normal operation.
failure of a component is far from normal and in this case full control
is what you want/need.
>Whether this simple way should belong to mdadm is another question, but
>I personnaly think it should, as it would introduce no overhead
>(would it, really ?) and would be very helpful.
>
>
KISS: keep it stupid simple
this is the philosophy. keep low-level tools stupid simple. more
complexity brings a higher risk of failure.
we're talking about raid. not about doing backups or syncing the system
clock.
>>did you ever thought about switching to a hardware where you can remove
>>and add disks without having to do anything else than pull the old one
>>out and push teh new one in?
>>
>>
>Ok, here we are...
>[First, the RAID controller I'm forced to deal with has no Linux
>driver, but that's not important for our discussion.]
>
>
there are some nice boxes arround. ther take a bunch of disks and appear
to the host as a simple SCSI disk. had such a thing in the past.
replacing disks was so simple a secretary could have done that. ;-)
>I don't agree with that. Using grep on vague patterns is not
>
>
i think grep is far more powerfull as you think.
>>the more you get used to it, the less "kludgy" they will be.
>>
>>
>Of course, but the very idea is that one shouldn't have to get used to
>it too much to perform simple and common actions.
>
>
if replacing disks is a common case to you, you should buy your disks
from a different manufacturer. ;-)
and if you have so many arrays that a disk failure is common because of
the number of disks, you would want to know the basics.
>But I guess we'll never agree anyway... :-(
>
>
we're just on different levels of usage. and there's a tool for everyone
on us.
my tool is mdadm.
and yours is EVMS or some other high level frontend which abstracts the
use of the low-level tools behind a nice looking UI.
greetings,
Frank
-
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:[~2005-04-19 19:46 UTC|newest]
Thread overview: 26+ messages / expand[flat|nested] mbox.gz Atom feed top
2005-04-19 11:00 Questions about software RAID bernd
2005-04-19 14:40 ` Hervé Eychenne
2005-04-19 15:27 ` David Greaves
2005-04-19 15:54 ` Hervé Eychenne
2005-04-19 16:53 ` Frank Wittig
2005-04-19 17:54 ` Hervé Eychenne
2005-04-19 19:46 ` Frank Wittig [this message]
2005-04-20 4:15 ` Guy
2005-04-20 4:47 ` Questions about software RAID - red led Alvin Oga
2005-04-20 7:59 ` Questions about software RAID David Greaves
2005-04-20 9:26 ` Molle Bestefich
2005-04-20 9:32 ` Hervé Eychenne
2005-04-20 17:36 ` Molle Bestefich
2005-04-20 11:16 ` Peter T. Breuer
2005-04-20 12:34 ` Lars Marowsky-Bree
2005-04-20 15:49 ` Martin K. Petersen
2005-04-21 1:21 ` Guy
-- strict thread matches above, loose matches on Subject: below --
2005-04-18 19:50 tmp
2005-04-18 20:12 ` David Greaves
2005-04-18 23:12 ` tmp
2005-04-19 6:36 ` Peter T. Breuer
2005-04-19 7:15 ` Luca Berra
2005-04-19 8:08 ` David Greaves
2005-04-19 12:18 ` Michael Tokarev
2005-04-18 20:15 ` Peter T. Breuer
2005-04-18 20:50 ` Frank Wittig
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=42656030.6000506@weisshuhn.de \
--to=fw@weisshuhn.de \
--cc=linux-raid@vger.kernel.org \
--cc=rv@eychenne.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).