* domap (0) failure for create/reload map
@ 2008-05-23 9:58 Laurent GEHLEN
2008-05-24 9:47 ` Laurent GEHLEN
0 siblings, 1 reply; 5+ messages in thread
From: Laurent GEHLEN @ 2008-05-23 9:58 UTC (permalink / raw)
To: dm-devel
[-- Attachment #1.1: Type: text/plain, Size: 1212 bytes --]
Hello,
Is there anybody who can help me to find where is my problem.
I'm trying to generate a mapper device with the tools multipath. But visibly
it blocs before it finish, because I don't have any new mapper device.
When i chose the verbose level 3 i can see those interesting things:
> # multipath -v3
> [...]
> sda: not found in pathvec
> [...]
> sdb: not found in pathvec
> [...]
> sdc: not found in pathvec
> [...]
> sdd: not found in pathvec
> [...]
> test: set ACT_CREATE (map does not exist)
> test: domap (0) failure for create/reload map
> [...]
> libdevmapper: libdm-common.c(239): Setting SELinux context for
> /dev/mapper/test to system_u:object_r:fixed_disk_device_t.
> [...]
>
I think the most interesting thing is the "domap (0) failure for
create/reload map".
I've read a bit about the code mutlipath
(cm/linux/storage/multipath-tools/libmultipath/configure.c+domap+(0)+failure+for+create/reload+map&hl=fr&ct=clnk&cd=4&gl=be&client=firefox-a)
And conclude (but not sure) that's the dm_addmap failed.
you can find the output of multipath -v3 here:
--> http://rafb.net/p/J45SFA12.html
My multipath.conf here:
--> http://rafb.net/p/G66QZ826.html
Thank you in advance for any idea!
Laurent
[-- Attachment #1.2: Type: text/html, Size: 1624 bytes --]
[-- Attachment #2: Type: text/plain, Size: 0 bytes --]
^ permalink raw reply [flat|nested] 5+ messages in thread
* Re: domap (0) failure for create/reload map
2008-05-23 9:58 domap (0) failure for create/reload map Laurent GEHLEN
@ 2008-05-24 9:47 ` Laurent GEHLEN
2008-06-03 9:01 ` Laurent GEHLEN
0 siblings, 1 reply; 5+ messages in thread
From: Laurent GEHLEN @ 2008-05-24 9:47 UTC (permalink / raw)
To: dm-devel
[-- Attachment #1.1: Type: text/plain, Size: 1640 bytes --]
I've just seen that the link are dead, so I uploaded the file on my server.
So now you can find the output of multipath -v3 here:
--> http://xen-lo.no-ip.org/temp/output-multipath-v3
And my multipath.conf here:
--> http://xen-lo.no-ip.org/temp/multipath.conf
<http://rafb.net/p/J45SFA12.html>
Thanks
Laurent
2008/5/23 Laurent GEHLEN <list.4.gehlen@gmail.com>:
> Hello,
>
> Is there anybody who can help me to find where is my problem.
> I'm trying to generate a mapper device with the tools multipath. But
> visibly it blocs before it finish, because I don't have any new mapper
> device.
> When i chose the verbose level 3 i can see those interesting things:
>
>> # multipath -v3
>> [...]
>> sda: not found in pathvec
>> [...]
>> sdb: not found in pathvec
>> [...]
>> sdc: not found in pathvec
>> [...]
>> sdd: not found in pathvec
>> [...]
>> test: set ACT_CREATE (map does not exist)
>> test: domap (0) failure for create/reload map
>> [...]
>> libdevmapper: libdm-common.c(239): Setting SELinux context for
>> /dev/mapper/test to system_u:object_r:fixed_disk_device_t.
>> [...]
>>
>
> I think the most interesting thing is the "domap (0) failure for
> create/reload map".
> I've read a bit about the code mutlipath
> (cm/linux/storage/multipath-tools/libmultipath/configure.c+domap+(0)+failure+for+create/reload+map&hl=fr&ct=clnk&cd=4&gl=be&client=firefox-a)
> And conclude (but not sure) that's the dm_addmap failed.
>
> you can find the output of multipath -v3 here:
> --> http://rafb.net/p/J45SFA12.html
>
> My multipath.conf here:
> --> http://rafb.net/p/G66QZ826.html
>
> Thank you in advance for any idea!
>
> Laurent
>
>
[-- Attachment #1.2: Type: text/html, Size: 2462 bytes --]
[-- Attachment #2: Type: text/plain, Size: 0 bytes --]
^ permalink raw reply [flat|nested] 5+ messages in thread
* Re: domap (0) failure for create/reload map
2008-05-24 9:47 ` Laurent GEHLEN
@ 2008-06-03 9:01 ` Laurent GEHLEN
2008-06-03 14:52 ` malahal
0 siblings, 1 reply; 5+ messages in thread
From: Laurent GEHLEN @ 2008-06-03 9:01 UTC (permalink / raw)
To: dm-devel
[-- Attachment #1.1: Type: text/plain, Size: 1971 bytes --]
I've find some more info in my /var/log/syslog:
kernel: device-mapper: table: 253:12: multipath: error getting device
kernel: device-mapper: ioctl: error adding target to table
Still no clue ?
Laurent
2008/5/24 Laurent GEHLEN <list.4.gehlen@gmail.com>:
> I've just seen that the link are dead, so I uploaded the file on my server.
>
> So now you can find the output of multipath -v3 here:
> --> http://xen-lo.no-ip.org/temp/output-multipath-v3
> And my multipath.conf here:
> --> http://xen-lo.no-ip.org/temp/multipath.conf
> <http://rafb.net/p/J45SFA12.html>
> Thanks
>
> Laurent
>
> 2008/5/23 Laurent GEHLEN <list.4.gehlen@gmail.com>:
>
> Hello,
>>
>> Is there anybody who can help me to find where is my problem.
>> I'm trying to generate a mapper device with the tools multipath. But
>> visibly it blocs before it finish, because I don't have any new mapper
>> device.
>> When i chose the verbose level 3 i can see those interesting things:
>>
>>> # multipath -v3
>>> [...]
>>> sda: not found in pathvec
>>> [...]
>>> sdb: not found in pathvec
>>> [...]
>>> sdc: not found in pathvec
>>> [...]
>>> sdd: not found in pathvec
>>> [...]
>>> test: set ACT_CREATE (map does not exist)
>>> test: domap (0) failure for create/reload map
>>> [...]
>>> libdevmapper: libdm-common.c(239): Setting SELinux context for
>>> /dev/mapper/test to system_u:object_r:fixed_disk_device_t.
>>> [...]
>>>
>>
>> I think the most interesting thing is the "domap (0) failure for
>> create/reload map".
>> I've read a bit about the code mutlipath
>> (cm/linux/storage/multipath-tools/libmultipath/configure.c+domap+(0)+failure+for+create/reload+map&hl=fr&ct=clnk&cd=4&gl=be&client=firefox-a)
>> And conclude (but not sure) that's the dm_addmap failed.
>>
>> you can find the output of multipath -v3 here:
>> --> http://rafb.net/p/J45SFA12.html
>>
>> My multipath.conf here:
>> --> http://rafb.net/p/G66QZ826.html
>>
>> Thank you in advance for any idea!
>>
>> Laurent
>>
>>
>
[-- Attachment #1.2: Type: text/html, Size: 3123 bytes --]
[-- Attachment #2: Type: text/plain, Size: 0 bytes --]
^ permalink raw reply [flat|nested] 5+ messages in thread
* Re: Re: domap (0) failure for create/reload map
2008-06-03 9:01 ` Laurent GEHLEN
@ 2008-06-03 14:52 ` malahal
2008-06-04 15:58 ` Laurent GEHLEN
0 siblings, 1 reply; 5+ messages in thread
From: malahal @ 2008-06-03 14:52 UTC (permalink / raw)
To: dm-devel
Laurent GEHLEN [list.4.gehlen@gmail.com] wrote:
> I've find some more info in my /var/log/syslog:
> kernel: device-mapper: table: 253:12: multipath: error getting device
> kernel: device-mapper: ioctl: error adding target to table
>
> Still no clue ?
>
> Laurent
Generally that means the devices you are trying to multipath are in use.
See if LVM has taken over them! What does "dmsetup table" tell you?
--Malahal.
^ permalink raw reply [flat|nested] 5+ messages in thread
* Re: Re: domap (0) failure for create/reload map
2008-06-03 14:52 ` malahal
@ 2008-06-04 15:58 ` Laurent GEHLEN
0 siblings, 0 replies; 5+ messages in thread
From: Laurent GEHLEN @ 2008-06-04 15:58 UTC (permalink / raw)
To: device-mapper development
[-- Attachment #1.1: Type: text/plain, Size: 2524 bytes --]
Yes I have LVM on the SAN Disk. But everything is on the sdd5. So i don't
see by what the sd{a,b,c} could be in use ...
# dmsetup table
san_vg_root-san_lv_home: 0 4096000 linear 8:53 4096384
san_vg_root-san_lv_opt: 0 4096000 linear 8:53 8192384
san_vg_root-san_lv_root: 0 4096000 linear 8:53 384
san_vg_root-san_lv_tmp: 0 4096000 linear 8:53 12288384
san_vg_root-san_lv_usr: 0 4096000 linear 8:53 16384384
san_vg_root-san_lv_var: 0 10240000 linear 8:53 20480384
# ls -l /dev/sd* | grep "$majeur, *$mineur"
brw-r----- 1 root disk 8, 0 May 21 13:22 /dev/sda
brw-r----- 1 root disk 8, 1 May 21 13:22 /dev/sda1
brw-r----- 1 root disk 8, 2 May 21 13:22 /dev/sda2
brw-r----- 1 root disk 8, 3 May 21 13:22 /dev/sda3
brw-r----- 1 root disk 8, 5 May 21 13:22 /dev/sda5
brw-r----- 1 root disk 8, 16 May 21 13:22 /dev/sdb
brw-r----- 1 root disk 8, 17 May 21 13:22 /dev/sdb1
brw-r----- 1 root disk 8, 18 May 21 13:22 /dev/sdb2
brw-r----- 1 root disk 8, 19 May 21 13:22 /dev/sdb3
brw-r----- 1 root disk 8, 21 May 21 13:22 /dev/sdb5
brw-r----- 1 root disk 8, 32 May 21 13:22 /dev/sdc
brw-r----- 1 root disk 8, 33 May 21 13:22 /dev/sdc1
brw-r----- 1 root disk 8, 34 May 21 13:22 /dev/sdc2
brw-r----- 1 root disk 8, 35 May 21 13:22 /dev/sdc3
brw-r----- 1 root disk 8, 37 May 21 13:22 /dev/sdc5
brw-r----- 1 root disk 8, 48 May 21 13:22 /dev/sdd
brw-r----- 1 root disk 8, 49 May 21 13:26 /dev/sdd1
brw-r----- 1 root disk 8, 50 May 21 13:22 /dev/sdd2
brw-r----- 1 root disk 8, 51 May 21 13:22 /dev/sdd3
brw-r----- 1 root disk 8, 53 May 21 13:22 /dev/sdd5
# pvdisplay
--- Physical volume ---
PV Name /dev/sdd5
VG Name san_vg_root
PV Size 149.83 GB / not usable 1.43 MB
Allocatable yes
PE Size (KByte) 4096
Total PE 38356
Free PE 34606
Allocated PE 3750
PV UUID i2xhAY-1xyK-cNg0-Sfob-v76b-Kc4e-L4NS7e
2008/6/3 <malahal@us.ibm.com>:
> Laurent GEHLEN [list.4.gehlen@gmail.com] wrote:
> > I've find some more info in my /var/log/syslog:
> > kernel: device-mapper: table: 253:12: multipath: error getting
> device
> > kernel: device-mapper: ioctl: error adding target to table
> >
> > Still no clue ?
> >
> > Laurent
>
> Generally that means the devices you are trying to multipath are in use.
> See if LVM has taken over them! What does "dmsetup table" tell you?
>
> --Malahal.
>
> --
> dm-devel mailing list
> dm-devel@redhat.com
> https://www.redhat.com/mailman/listinfo/dm-devel
>
[-- Attachment #1.2: Type: text/html, Size: 3925 bytes --]
[-- Attachment #2: Type: text/plain, Size: 0 bytes --]
^ permalink raw reply [flat|nested] 5+ messages in thread
end of thread, other threads:[~2008-06-04 15:58 UTC | newest]
Thread overview: 5+ messages (download: mbox.gz follow: Atom feed
-- links below jump to the message on this page --
2008-05-23 9:58 domap (0) failure for create/reload map Laurent GEHLEN
2008-05-24 9:47 ` Laurent GEHLEN
2008-06-03 9:01 ` Laurent GEHLEN
2008-06-03 14:52 ` malahal
2008-06-04 15:58 ` Laurent GEHLEN
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.