From: Wilfried Weissmann <Wilfried.Weissmann@gmx.at>
To: Kernel Mailing List <linux-kernel@vger.kernel.org>, dm-devel@sistina.com
Cc: Arjan van de Ven <arjanv@redhat.com>
Subject: kernel 2.6 biosraid via device mapper - partition support
Date: Sun, 11 Jan 2004 16:21:53 +0100 [thread overview]
Message-ID: <40016A11.90605@gmx.at> (raw)
hello,
i just started to investigate how biosraid support for the HPT37X
IDE-chipsets can be implemented in the 2.6 kernel. implementing the
basic raid levels (0, 1, 0+1, JBOD) seems to be pretty straight forward.
this can be done by reading the raid signatures of the disks and then
pipeing the configuration through dmsetup or using the libdevmapper
library directly. what bothers me is the partition support. the number
of minor device nodes that are registered per mapped block device is 1.
this means that there is no way that the kernel does the
partition-handling by itself. the alternative is to do the partition
scanning in userspace and to use another device mapper layer to create
the partition device nodes. it appears that this was already suggested
by Christophe Varoqui ( http://lwn.net/Articles/13958/ ) but this
project is now idle. this also has the disadvantage that any changes in
the partitioning of the raid volume (e.g. by using *fdisk, distribution
installers, ...) require a manual re-invocation of the biosraid setup
tool. plus the whole code under linux/fs/partitions/... has to be
duplicated so that not only the dos partitioning scheme is supported,
but also BSD slices, x86 solaris, windows dynamic disks, ...
which way to go? is there another solution that i have missed?
regards,
Wilfried
next reply other threads:[~2004-01-11 15:22 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-01-11 15:21 Wilfried Weissmann [this message]
2004-01-11 19:34 ` [dm-devel] kernel 2.6 biosraid via device mapper - partition support Christophe Saout
2004-01-11 20:33 ` partition detection in 2.7 Jeff Garzik
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=40016A11.90605@gmx.at \
--to=wilfried.weissmann@gmx.at \
--cc=arjanv@redhat.com \
--cc=dm-devel@sistina.com \
--cc=linux-kernel@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