From: Carl-Daniel Hailfinger <c-d.hailfinger.kernel.2004@gmx.net>
To: Wilfried Weissmann <Wilfried.Weissmann@gmx.at>
Cc: Jeff Garzik <jgarzik@pobox.com>,
Arjan van de Ven <arjanv@redhat.com>,
"Kevin P. Fleming" <kpfleming@backtobasicsmgmt.com>,
Linux Kernel Mailing List <linux-kernel@vger.kernel.org>,
Bartlomiej Zolnierkiewicz <B.Zolnierkiewicz@elka.pw.edu.pl>,
Device mapper devel list <dm-devel@redhat.com>,
Thomas Horsten <thomas@horsten.com>,
medley@lists.infowares.com
Subject: Re: ATARAID/FakeRAID/HPTRAID/PDCRAID as dm targets?
Date: Thu, 01 Apr 2004 05:06:09 +0200 [thread overview]
Message-ID: <406B8721.6080104@gmx.net> (raw)
In-Reply-To: <4060A8E0.7020905@gmx.at>
Wilfried Weissmann wrote:
> Jeff Garzik wrote:
>
>> Carl-Daniel Hailfinger wrote:
>>
>>>> 4. nice clickety-click user interface
>>>> Especially useful for lazy people like me. ;)
>>>
>>>
>>>
>>>
>>> I prefer the "no user interface" approach. But then again, I'm biased.
>>
>>
>>
>> Agreed -- a minimal implementation is needed first anyway. The BIOS
>> of these proprietary RAID thingies typically provides the user interface.
>
>
> On the other hand EVMS allowed me to make a minimal solution by taking
> care of the partitioning and the DM-API in the EVMS framework. The user
After having written a generic standalone solution (currently in testing)
with less code than the evms plugin, I have my doubts about EVMS allowing
minimal solutions. It seems most of your plugin is just code to make EVMS
happy and I was frightened by that.
> interface is just an add-on that comes with the package. Right now its
> just a way for the user to get a "look its really there". If we do the
> RAID configuration and writeing the configuration blocks to the disks or
> not is in your hands. When we consider this to be to risky then lets
> just skip it.
Please do not misunderstand my intentions. I appreciate your code very
much and tried to reuse as much of it as possible (and tried to keep my
modifications small), and if you plan on integrating my generic code into
EVMS you're most welcome (I would feel honoured).
However, my goals were (in that order):
1. Spit out a list of devices that have some sort of RAID magic
2. Group the devices by array
3. Set up a device corresponding to /dev/araraid/d0
and keep the code generic and independent enough so that it can be
integrated into EVMS or used standalone with only a few changes.
Code will follow once I get step 3 working generically.
Step 1 is done (I have some trouble finding the superblock on small
PDCRAID arrays, will ask Jeff).
Step 2 is done (modulo implementation bugs not yet found)
Step 3 is partly done (It only works for striped Highpoint arrays because
I didn't have the hardware available until now)
Regards,
Carl-Daniel
next prev parent reply other threads:[~2004-04-01 3:03 UTC|newest]
Thread overview: 21+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-03-20 18:19 ATARAID/FakeRAID/HPTRAID/PDCRAID as dm targets? Carl-Daniel Hailfinger
2004-03-20 20:51 ` Jeff Garzik
2004-03-21 2:23 ` Kevin P. Fleming
2004-03-21 7:47 ` Arjan van de Ven
2004-03-21 13:47 ` Wilfried Weissmann
2004-03-22 19:14 ` Carl-Daniel Hailfinger
2004-03-22 19:29 ` Jeff Garzik
2004-03-23 21:15 ` Wilfried Weissmann
2004-04-01 3:06 ` Carl-Daniel Hailfinger [this message]
2004-04-01 3:19 ` Carl-Daniel Hailfinger
2004-04-01 5:28 ` Jeff Garzik
2004-03-23 21:03 ` Wilfried Weissmann
2004-03-21 18:07 ` Jeff Garzik
2004-03-21 18:40 ` Carl-Daniel Hailfinger
2004-03-21 18:45 ` Kevin P. Fleming
2004-03-21 19:44 ` Carl-Daniel Hailfinger
2004-03-21 20:01 ` Carl-Daniel Hailfinger
2004-03-21 20:19 ` christophe varoqui
2004-03-22 11:46 ` Carl-Daniel Hailfinger
2004-03-21 18:58 ` Måns Rullgård
2004-03-24 18:21 ` Pedro Larroy
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=406B8721.6080104@gmx.net \
--to=c-d.hailfinger.kernel.2004@gmx.net \
--cc=B.Zolnierkiewicz@elka.pw.edu.pl \
--cc=Wilfried.Weissmann@gmx.at \
--cc=arjanv@redhat.com \
--cc=dm-devel@redhat.com \
--cc=jgarzik@pobox.com \
--cc=kpfleming@backtobasicsmgmt.com \
--cc=linux-kernel@vger.kernel.org \
--cc=medley@lists.infowares.com \
--cc=thomas@horsten.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