Hi, I am able to bind the dm device with raw device successfully but when trying to open in READ/WRITE mode , the application is not able to open . For binding the raw device I have used the RAW_SETBIND/RAW_GETBIND ioctls. raw -qa shows the raw device is bounded to device-maper device. [root@ioctl]# raw -qa /dev/raw/raw1: bound to major 253, minor 1 [root@ioctl]#ls /dev/mapper/mpath103 -l brw-rw---- 1 root disk 253, 1 Jul 3 16:18 /dev/mapper/mpath103 If any one used the raw device which is bound to device-mapper device using the RAW_SETBIND/RAW_GETBIND,please help. TIA Santosh -----Original Message----- From: dm-devel-bounces@xxxxxxxxxx [mailto:dm-devel-bounces@xxxxxxxxxx] On Behalf Of Milan Broz Sent: Wednesday, June 21, 2006 6:57 PM To: device-mapper development Subject: Re: Next set of device-mapper patches AJ Lewis wrote: > 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? Currently supported for simple mapping with single target only, if there are more than one target, it will fail with error -ENOTTY. Milan -- Milan Broz mbroz@xxxxxxxxxx -- dm-devel@xxxxxxxxxx https://www.redhat.com/mailman/listinfo/dm-devel -- dm-devel@xxxxxxxxxx https://www.redhat.com/mailman/listinfo/dm-devel
