From: Luca Berra <bluca@comedia.it>
To: linux-lvm@redhat.com
Subject: Re: [linux-lvm] Re: LVM2 on top of RAID1? (x86_64)
Date: Thu Feb 12 15:05:01 2004 [thread overview]
Message-ID: <402BDCAB.5060202@comedia.it> (raw)
In-Reply-To: <402BC89E.6020606@backtobasicsmgmt.com>
Kevin P. Fleming wrote:
> Luca Berra wrote:
>
>> i still believe it would be better if lvm ignored md component devices
>> completely.
>
>
> In kernel 2.6 land this is easy to do as well (for everything, not just
> MD). When vgscan tries to open the device to read metadata, open it with
> O_EXCL. If any other kernel subsystem is currently using the device,
> then the open() will fail and vgscan can ignore the device.
this won't help if the device is not yet opened by md
i posted a patch to this list that checks for an md superblock.
i am pushing for consideration of this approach.
L.
next prev parent reply other threads:[~2004-02-12 20:06 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-02-12 10:10 [linux-lvm] Re: LVM2 on top of RAID1? (x86_64) Douglas Kilpatrick
2004-02-12 12:41 ` Luca Berra
2004-02-12 13:40 ` Kevin P. Fleming
2004-02-12 15:05 ` Luca Berra [this message]
2004-02-12 15:30 ` Joe Thornber
2004-02-12 15:54 ` Luca Berra
-- strict thread matches above, loose matches on Subject: below --
2004-02-09 10:36 [linux-lvm] " Douglas Kilpatrick
2004-02-09 10:43 ` [linux-lvm] " Måns Rullgård
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=402BDCAB.5060202@comedia.it \
--to=bluca@comedia.it \
--cc=linux-lvm@redhat.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.