From: Heinz Mauelshagen <mauelsha@ez-darmstadt.telekom.de>
To: linux-lvm@msede.com
Subject: Re: [linux-lvm] Swap/DB devices (fwd)
Date: Sat, 17 Apr 1999 13:22:29 METDST [thread overview]
Message-ID: <199904171124.AA07700@mailgate1b.telekom.de> (raw)
On Sat, 17 Apr 1999 01:14:00 +0100 (BST), Stephen Tweedie
<sct@redhat.com> wrote:
>
> On Fri, 16 Apr 1999 23:47:06 METDST, Heinz Mauelshagen
> <mauelsha@ez-darmstadt.telekom.de> said:
>
> >> I'm curious: why? I would have thought that LVM should support any
> >> requests coming in through ll_rw_block already.
>
> > It's simply a matter of userland (lv_create_node() and friends in lvmlib)
> > to create the LVM 'raw' device specials.
> > Only regular buffer cached device specials are created up to 0.6.
>
> You won't need to. The raw device patches create one single new major
> number, and let you bind the minor numbers to any block devices you
> want. You can access _any_ block device driver without modification.
>
The LVM lib creates the device special nodes dynamically if a logical volume
is created by lvcreate(8) or found by vgscan(8)/vgimport(8).
LVM function lv_create_node() has to be extended to create the raw device too.
The LVM driver can then be accessed by that raw device node
_without_ modification.
Heinz
--
=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-
Systemmanagement C/S Deutsche Telekom AG
Entwicklungszentrum Darmstadt
Heinz Mauelshagen Otto-Roehm-Strasse 71c
Senior Systems Engineer Postfach 10 05 41
64205 Darmstadt
mge@ez-darmstadt.telekom.de Germany
+49 6151 886-425
FAX-386
=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-
next reply other threads:[~1999-04-17 11:22 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
1999-04-17 11:22 Heinz Mauelshagen [this message]
1999-04-17 20:03 ` [linux-lvm] Swap/DB devices Stephen C. Tweedie
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=199904171124.AA07700@mailgate1b.telekom.de \
--to=mauelsha@ez-darmstadt.telekom.de \
--cc=linux-lvm@msede.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.