From: Wilfried Weissmann <Wilfried.Weissmann@gmx.at>
To: Sergey Vlasov <vsu@altlinux.ru>, evms-devel@lists.sourceforge.net
Cc: Kernel Mailing List <linux-kernel@vger.kernel.org>
Subject: Re: [Evms-devel] Re: evms plugin for hptraid support <<<pre-alpha>>>
Date: Tue, 09 Mar 2004 20:34:26 +0100 [thread overview]
Message-ID: <404E1C42.8040707@gmx.at> (raw)
In-Reply-To: <20040309143131.098c1033.vsu@altlinux.ru>
Sergey Vlasov wrote:
> On Fri, 27 Feb 2004 22:16:33 +0100 Wilfried Weissmann wrote:
>
>
>>this is my attempt to add support for the ataraid devices to the 2.6
>>kernel. the code is as far as possible from being mature and useable as
>>one could imagine (i have not even requested any plugin-ids for the evms
>>engine). for now it only detects the HPT370A controller, because of i am
>> checking the pci-ids of the controller to prevent that any non-raid
>>disks are stolen by the raid module. this would happen with the current
>>ataraid code from the kernel v2.4.
>
>
> I'm not sure if this PCI ID checking is a good thing. With ataraid
> drivers, if your FakeRAID controller gets broken for some reason, you
> can just attach the disks to any available IDE controller and get
> access to your data. With the proposed PCI ID check this ability will
> be lost.
>
> The problem with stale RAID superblocks on disks may be solved by
> adding a command to clear the RAID superblocks without touching the
> rest of data.
I can create a configuration option that controls or disables the PCI
check. Claiming all disks that have raid signatures is a great feature
for debugging and disaster recovery, but I think that if this is the
default then it is more trouble than it is worth.
Regards,
Wilfried
prev parent reply other threads:[~2004-03-09 19:44 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-02-27 21:16 evms plugin for hptraid support <<<pre-alpha>>> Wilfried Weissmann
[not found] ` <20040309143131.098c1033.vsu@altlinux.ru>
2004-03-09 19:34 ` 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=404E1C42.8040707@gmx.at \
--to=wilfried.weissmann@gmx.at \
--cc=evms-devel@lists.sourceforge.net \
--cc=linux-kernel@vger.kernel.org \
--cc=vsu@altlinux.ru \
/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