From: AJ Lewis <aj@terrascale.com>
To: device-mapper development <dm-devel@redhat.com>
Subject: Re: Next set of device-mapper patches
Date: Wed, 21 Jun 2006 08:07:15 -0500 [thread overview]
Message-ID: <20060621130620.GA11880@fenrir.local> (raw)
In-Reply-To: <4499310F.3000007@redhat.com>
[-- Attachment #1.1: Type: text/plain, Size: 697 bytes --]
On Wed, Jun 21, 2006 at 01:44:15PM +0200, Milan Broz wrote:
> ioctl patch simple route ioctls to underlying block device
> -> it supports all ioctl which are supported by your physical device.
>
> e.g.
> in simple case you have volume /dev/mapper/VolGroup00-LogVol0
> mapped to physical device /dev/sda, inquiry ioctl (using tools from
> sg3_util)
> sg_inq /dev/sda
> is the same as
> sg_inq /dev/mapper/VolGroup00-LogVol0
>
> In the case of multipath target ioctl command is sent through
> active path.
So what happens when you have multiple block devices in the volume? And what
if those block devices have different levels of support for the ioctls?
--
AJ Lewis
[-- Attachment #1.2: Type: application/pgp-signature, Size: 186 bytes --]
[-- Attachment #2: Type: text/plain, Size: 0 bytes --]
next prev parent reply other threads:[~2006-06-21 13:07 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <3EC60E80D9AA7C4E910ACC9DA2003AC30606C55C@BGEEXC02.asiapacific.cpqcorp.net>
2006-06-21 11:44 ` Next set of device-mapper patches Milan Broz
2006-06-21 13:07 ` AJ Lewis [this message]
2006-06-21 13:26 ` Milan Broz
2006-07-03 16:29 ` Singh, Santosh (STSD)
[not found] <20060610160024.36F82733FA@hormel.redhat.com>
2006-06-15 14:52 ` Singh, Santosh (STSD)
2006-06-15 14:56 ` Next " Alasdair G Kergon
2006-06-15 15:12 ` Singh, Santosh (STSD)
2006-06-15 15:20 ` Alasdair G Kergon
2006-06-15 15:46 ` Singh, Santosh (STSD)
2006-06-15 16:16 ` Alasdair G Kergon
2006-06-16 14:31 ` Singh, Santosh (STSD)
2006-06-16 14:36 ` Singh, Santosh (STSD)
2006-06-09 21:22 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=20060621130620.GA11880@fenrir.local \
--to=aj@terrascale.com \
--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.