All of lore.kernel.org
 help / color / mirror / Atom feed
From: Christophe Varoqui <christophe.varoqui@free.fr>
To: device-mapper development <dm-devel@redhat.com>
Subject: Re: Adding/removing multi-pathed disk partitions
Date: Thu, 17 Feb 2005 23:38:40 +0100	[thread overview]
Message-ID: <42151CF0.90709@free.fr> (raw)
In-Reply-To: <C2EEB4E538D3DC48BF57F391F422779321A708@SRMANNING.eng.emc.com>

goggin, edward wrote:

>Should one be using the multi-path device-mapper mapped device
>name or one of the SCSI target device names for the whole disk
>device when modifying a SCSI disk's partition table with fdisk(8)?
>
>If the former, drivers/block/ioctl.c:blkdev_reread_part()
>currently returns EINVAL since the mapped device is not
>partitionable.  I can't imagine the recommendation is the
>latter, since there is no mechanism in place to synchronize
>the kernel's partition table handling amongst multiple target
>devices.
>
>--
>
As discussed earlier, one face of this problem is that kpartx does 
buffered reads to grab the on-disk partition table, leading to 
situations where kpartx ->fdisk -> kpartx sequence does not garanty 
partitons-to-maps layout will reflect reality.

To address this particular problem, do you think adding O_DIRECT to the 
open() call in kpartx.c would be enough ?

Regards,
cvaroqui

--
dm-devel mailing list
dm-devel@redhat.com
https://www.redhat.com/mailman/listinfo/dm-devel

  parent reply	other threads:[~2005-02-17 22:38 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2005-01-25 21:07 Adding/removing multi-pathed disk partitions goggin, edward
2005-01-25 22:34 ` christophe varoqui
2005-01-26  8:52   ` Lars Marowsky-Bree
2005-02-17 22:38 ` Christophe Varoqui [this message]
  -- strict thread matches above, loose matches on Subject: below --
2005-01-31 14:05 goggin, edward

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=42151CF0.90709@free.fr \
    --to=christophe.varoqui@free.fr \
    --cc=dm-devel@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.