linux-lvm.redhat.com archive mirror
 help / color / mirror / Atom feed
From: Luca Berra <bluca@comedia.it>
To: device-mapper development <dm-devel@redhat.com>,
	"ATARAID (eg, Promise Fasttrak,
	Highpoint 370) related discussions" <ataraid-list@redhat.com>
Cc: linux-lvm@redhat.com
Subject: [linux-lvm] Re: LVM on dmraid breakage
Date: Thu, 2 Aug 2007 08:50:12 +0200	[thread overview]
Message-ID: <20070802065012.GA28687@percy.comedia.it> (raw)
In-Reply-To: <46B0EAEF.6090305@cfl.rr.com>

On Wed, Aug 01, 2007 at 04:19:59PM -0400, Phillip Susi wrote:
>I am investigating a bug report involving the combination of lvm and 
>dmraid, and it seems to me that the problem is that lvm is detecting the 
>underlying partition on the primary disk and accessing it directly 
>rather than going through the raid device made by dmraid.  I think that 
>the problem is there is no facility for dmraid to "claim" the physical 
>disk so that lvm does not look at it, and also to have lvm scan the raid 
>device for physical volumes.
>
>Does anyone have any thoughts on how this might be accomplished?

Two things come to mind
1) dmraid should use ioctl BLKPG_DEL_PARTITION, to clean up any eventual
partition table on component devices

2) lvm tool filter could be modified to check if a device has been
already claimed by device-mapper.

something along the lines of:
ioctl DM_LIST_DEVICES
while (...)
  ioctl DM_TABLE_DEPS

the above would probably require a cache.


i believe that manual use of partx or lvm filters is sub-optimal
L.



-- 
Luca Berra -- bluca@comedia.it
        Communication Media & Services S.r.l.
 /"\
 \ /     ASCII RIBBON CAMPAIGN
  X        AGAINST HTML MAIL
 / \

       reply	other threads:[~2007-08-02  6:50 UTC|newest]

Thread overview: 19+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <46B0EAEF.6090305@cfl.rr.com>
2007-08-02  6:50 ` Luca Berra [this message]
2007-08-02 10:45   ` [linux-lvm] Re: LVM on dmraid breakage Bryn M. Reeves
2007-08-03  7:55     ` Luca Berra
     [not found]     ` <46B251BB.1010004@cfl.rr.com>
2007-08-03  0:40       ` [linux-lvm] Re: [dm-devel] " David Robinson
2007-08-07 21:37         ` Alasdair G Kergon
2007-08-07 21:03       ` Alasdair G Kergon
     [not found]         ` <46BA2FCC.1040001@cfl.rr.com>
2007-08-08 21:45           ` Alasdair G Kergon
     [not found]             ` <46BB4E86.7090000@cfl.rr.com>
2007-08-10  5:09               ` Luca Berra
2007-08-10 13:49               ` Alasdair G Kergon
     [not found]   ` <46B254E4.60700@cfl.rr.com>
2007-08-03  8:11     ` Luca Berra
     [not found]       ` <46B36F7A.2090601@cfl.rr.com>
2007-08-03 19:57         ` Luca Berra
     [not found]           ` <46B39E58.2040305@cfl.rr.com>
2007-08-04  6:50             ` Luca Berra
     [not found]               ` <46B733EE.4090507@cfl.rr.com>
2007-08-07  9:17                 ` Luca Berra
2007-08-07 22:01                   ` Alasdair G Kergon
2007-08-07 21:53             ` Alasdair G Kergon
2007-08-07 21:50         ` Alasdair G Kergon
2007-08-07 21:40       ` Alasdair G Kergon
2007-08-07 21:28     ` Alasdair G Kergon
2007-08-07 21:02   ` Alasdair G Kergon

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=20070802065012.GA28687@percy.comedia.it \
    --to=bluca@comedia.it \
    --cc=ataraid-list@redhat.com \
    --cc=dm-devel@redhat.com \
    --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 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).