From: Wilfried Weissmann <Wilfried.Weissmann@gmx.at>
To: Carl-Daniel Hailfinger <c-d.hailfinger.kernel.2004@gmx.net>
Cc: Thomas Horsten <thomas@horsten.com>,
Linux Kernel Mailing List <linux-kernel@vger.kernel.org>,
medley@lists.infowares.com,
linux-hotplug-devel@lists.sourceforge.net,
Jeff Garzik <jgarzik@pobox.com>,
Bartlomiej Zolnierkiewicz <B.Zolnierkiewicz@elka.pw.edu.pl>,
Greg KH <greg@kroah.com>
Subject: Re: [RFC] [DRAFT] [udev PATCH] First attempt at vendor RAID support
Date: Sat, 01 May 2004 16:31:04 +0000 [thread overview]
Message-ID: <4093D0C8.5010905@gmx.at> (raw)
In-Reply-To: <40803C61.503@gmx.net>
Hi,
I just returned from my vacation and checked my emails. That's why the
response is so late.
Carl-Daniel Hailfinger wrote:
>>>- People checking the numerous FIXMEs
>
>
> I now have the following FIXMEs (aka "I have no idea about it"):
> - 5 FIXMEs in the Medley RAID code. Thomas, could you comment once you're
> back?
> - 3 FIXMEs in the Highpoint RAID code. Wilfried, could you please take a
> look at them?
1) FIXME: Does "no array defined" correspond to HPT_T_SINGLEDISK?
I have to check this but I believe it is so.
2) FIXME: Is HPT_T_RAID_01_RAID_1 a value that can ever be found?
I think this is the new style raid-10 format that is supported by hpt374
and upwards. I do not have such a controller so I cannot verify this.
3) FIXME: what does HPT_MAGIC_BAD mean?
You get this if you pull one disk out of a raid-0 array for example. The
HPT-BIOS detects that the raid is not operational and marks the array as
bad (writes the HPT_MAGIC_BAD to the remaining disks).
[snip]
>>>- More data about Medley/Highpoint vendor superblocks (can I check for
>>>bogus values?)
>
>
> Wilfried, is there any consistency check I can add for Highpoint?
I have not found any crc or so. But since HPT marks any disks that is
not in an array as HPT_T_SINGLEDISK or HPT_MAGIC_BAD we should be fine
unless someone writes some garbage to the superblock.
>
>
>
>>>- Help with sorting out who owns which copyrights
>
>
> This is still a _big issue_.
The HPT copyrights look fine.
I am looking forward to see the part that writes the dm configuration so
that I can integrate it into the evms plugin.
bye,
wilfried
PS: add_disk_to_raidlists() does never return retval!
-------------------------------------------------------
This SF.Net email is sponsored by: Oracle 10g
Get certified on the hottest thing ever to hit the market... Oracle 10g.
Take an Oracle 10g class now, and we'll give you the exam FREE.
http://ads.osdn.com/?ad_id149&alloc_idÅ66&op=click
_______________________________________________
Linux-hotplug-devel mailing list http://linux-hotplug.sourceforge.net
Linux-hotplug-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/linux-hotplug-devel
prev parent reply other threads:[~2004-05-01 16:31 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-04-15 0:24 [RFC] [DRAFT] [udev PATCH] First attempt at vendor RAID support in Carl-Daniel Hailfinger
2004-04-15 14:08 ` [RFC] [DRAFT] [udev PATCH] First attempt at vendor RAID support Thomas Horsten
2004-04-16 20:04 ` Carl-Daniel Hailfinger
2004-04-17 17:35 ` Carl-Daniel Hailfinger
2004-04-21 17:34 ` Jeff Garzik
2004-05-01 16:31 ` Wilfried Weissmann [this message]
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=4093D0C8.5010905@gmx.at \
--to=wilfried.weissmann@gmx.at \
--cc=B.Zolnierkiewicz@elka.pw.edu.pl \
--cc=c-d.hailfinger.kernel.2004@gmx.net \
--cc=greg@kroah.com \
--cc=jgarzik@pobox.com \
--cc=linux-hotplug-devel@lists.sourceforge.net \
--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;
as well as URLs for NNTP newsgroup(s).