Device Mapper Table 253 0 Multipath Error Getting Device
Contents |
Re: [dm-devel] Fwd: multipath errors Date: Fri, 27 Sep 2013 15:11:04 -0500 On Mon, Sep 23, 2013 at 11:09:18AM +0300, Amitai Alkalay wrote: > Hi, > Sorry for bumping, but I will appreciate any help on this matter.. > Thanks, > Amitai device-mapper ioctl error adding target to table multipath > > ---------- Forwarded message ---------- > From: Amitai Alkalay <[1]amitai alkalay work gmail com> kernel device-mapper ioctl error adding target to table > Date: Tue, Sep 10, 2013 at 2:29 PM > Subject: multipath errors > To: [2]dm-devel redhat com > > hi, > rhel multipath error getting device I sometimes see cases where io failed after some path failover, although > there are other valid paths. > I seem to get a lot of the following errors during a path removal > (failover): >
Device-mapper: Table 253:5: Multipath: Error Getting Device
> Aug 1 08:59:37 lg641 multipathd: 3514f0c532d80000a: failed in domap for removal of path sdcy > Aug 1 08:59:37 lg641 multipathd: uevent trigger error > Aug 1 08:59:37 lg641 multipathd: sdt: remove path (uevent) > Aug 1 08:59:37 lg641 kernel: device-mapper: table: 253:5: multipath: error getting device > Aug 1 08:59:37 lg641 kernel: device-mapper: ioctl: error adding target to table > Aug 1 08:59:37 lg641 multipathd: 3514f0c532d800001: load table [0 21474836480 multipath 0 0 device mapper table 252 0 multipath error getting device 1 1 queue-length 0 12 1 66:240 1 66:80 1 70:192 1 71:96 1 67:176 1 67:112 1 71:224 1 128:128 1 8: > 16 1 69:16 1 69:32 1 8:32 1] > Aug 1 08:59:37 lg641 multipathd: sdt: path removed from map 3514f0c532d800001f > > All the other paths are there, and still multipath decided to fail the io > with no apparent reason.� > > I would appreciate any comment about: > > 1. How can this happen. It shouldn't. The kernel should check through all of the paths before failing. Sometimes some actions on storage arrays temporarily bring all paths down, but even in that case, you should see messages in the logs of multipath trying all the paths before it fails. > 2. How can I increase the log level to understand multipath decisions. in /etc/multipath.conf defaults { ... verbosity 3 } This will add a lot of extra logging. Make sure that your logging isn't rate limited, or you will miss messages exactly when it's most important to see them. > 3. Why do I always see the errors regarding adding target to table. > The only thing I can think think about, that multipath temporarily > bypassed the other paths (maybe it got busy several times and gave up). > I'm usingï
[dm-devel] how to troubleshoot faulty multipath path? Date: Sat, 17 Dec 2011 11:34:50 +0100 Hello Mr Moger, Quoting "Moger, Babu"
Docker Device-mapper: Ioctl: Error Adding Target To Table
does your multipath.conf look like. Can you paste that as well. You messages file might help also. I have attached
Device-mapper: Ioctl: Error Adding Target To Table Suse
the output of multipath -ll. My multipath.conf only has some aliases defined, so I didn't attach that. I'm using the default config. I've grepped through the messages, dmesg and kern.log files. I https://www.redhat.com/archives/dm-devel/2013-September/msg00168.html have attached them. (Adding the full files isn't possible they have other application level output too.) I forgot to mention, I'm using 0.4.8+git0.761c66f-9 of multipath-tools. (Debian stable) Thanks in advance! -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- Rudy Gevaert e-mail: Rudy Gevaert UGent be Directie ICT, Afdeling https://www.redhat.com/archives/dm-devel/2011-December/msg00041.html Infrastructuur Groep Systemen tel: +32 9 264 4750 Universiteit Gent fax: +32 9 264 4994 Krijgslaan 281, gebouw S9, 9000 Gent, Belgie www.UGent.be -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- [1850209.907285] device-mapper: ioctl: unable to remove open device mailstore21 [1850569.600287] device-mapper: ioctl: unable to remove open device mailstore21 [1850892.506649] device-mapper: ioctl: unable to remove open device mailstore21 [1851106.061424] device-mapper: ioctl: device doesn't appear to be in the dev hash table. [4895914.569949] device-mapper: table: 253:31: multipath: error getting device [4895914.569989] device-mapper: ioctl: error adding target to table [4895914.590736] device-mapper: table: 253:31: multipath: error getting device [4895914.590776] device-mapper: ioctl: error adding target to table [4896672.904187] device-mapper: table: 253:31: multipath: error getting device [4896672.904226] device-mapper: ioctl: error adding target to table [4896672.915275] device-mapper: table: 253:31: multipath: error getting device [4896672.915311] device-mapper: ioctl: error adding target to table [4896999.249946] device-mapper: table: 253:31: multipath: error getting device [4896999.249985] device-mapper: ioctl: error adding target to table [4896999.289079] device-mapper: table: 253:31: multipath: error getting device [4896999.289116] device-mapper: ioctl: error adding target to tablekern.log:Dec 16 16:20:13 cyrprd2 kernel: [4895914.569949] device-mapper: table: 253:31: m
Issues Roadmap View Issue Details[Jump to Notes] [Issue History] [Print] IDProjectCategoryView StatusDate SubmittedLast Update0003290CentOS-5device-mapper-multipathpublic2008-12-08 16:112008-12-11 12:15ReporterfinistPrioritynormalSeveritymajorReproducibilityalwaysStatusfeedbackResolutionopenProduct Version5.2Target VersionFixed in VersionSummary0003290: multipath does not https://bugs.centos.org/view.php?id=3290 work (device-mapper: table: 253:0: multipath: error getting device)Descriptioni've faced a strange http://unix.stackexchange.com/questions/122947/device-mapper-on-rhel6-unable-to-create-devs-for-lvm-logical-volume issue with multipathing: the goal is to install CentOS5.2 and use multipath root device. 1) CentOS 4.x work fine 2) CentOS 5.2 installs fine (with installation command "linux mpath"), but the resulting systems seems not using multipath: [root@localhost ~]# l /dev/mapper/ total 0 1217 drwxr-xr-x error getting 2 root 60 Dec 8 17:41 ./ 1214 drwxr-xr-x 10 root 14320 Dec 8 17:44 ../ 4795 crw------- 1 root 10, 63 Dec 8 17:41 control [root@localhost ~]# multipath -v2 [root@localhost ~]# multipath -v2 -d create: mpath0 (3600508b400011c130003000000fc0000) COMPAQ,HSV111 (C)COMPAQ [size=100G][features=0][hwhandler=1 hp-sw] \_ round-robin 0 [prio=4][undef] \_ 0:0:0:1 sda 8:0 [undef][ready] \_ 0:0:1:1 sdb 8:16 [undef][ready] \_ error getting device 1:0:0:1 sdc 8:32 [undef][ready] \_ 1:0:1:1 sdd 8:48 [undef][ready] [root@localhost ~]# cat /etc/multipath.conf defaults { user_friendly_names yes } blacklist { devnode "^(ram|raw|loop|fd|md|dm-|sr|scd|st)[0-9]*" devnode "^(hd|xvd)[a-z]*" wwid "*" } # Make sure our multipath devices are enabled. blacklist_exceptions { wwid "3600508b400011c130003000000fc0000" } multipaths { multipath { wwid "3600508b400011c130003000000fc0000" alias mpath0 } } devices { device { vendor "HP|COMPAQ*" product "HSV1*" hardware_handler "1 hp-sw" path_grouping_policy group_by_prio } } The error happens on "reload" ioctl: [root@localhost ~]# multipath -v9 ... mpath0: pgfailover = -1 (internal default) mpath0: pgpolicy = failover (internal default) mpath0: selector = round-robin 0 (internal default) mpath0: features = 0 (internal default) mpath0: hwhandler = 1 hp-sw (controller setting) mpath0: rr_weight = 1 (internal default) mpath0: minio = 1000 (config file default) mpath0: no_path_retry = NONE (internal default) pg_timeout = NONE (internal default) mpath0: set ACT_CREATE (map does not exist) libdevmapper: ioctl/libdm-iface.c(1623): device-mapper: reload ioctl failed: Invalid argument mpath0: domap (0) failure for create/reload map mpath0: remove multipath map ... dmesg after that shows several pairs of following messages: dev
here for a quick overview of the site Help Center Detailed answers to any questions you might have Meta Discuss the workings and policies of this site About Us Learn more about Stack Overflow the company Business Learn more about hiring developers or posting ads with us Unix & Linux Questions Tags Users Badges Unanswered Ask Question _ Unix & Linux Stack Exchange is a question and answer site for users of Linux, FreeBSD and other Un*x-like operating systems. Join them; it only takes a minute: Sign up Here's how it works: Anybody can ask a question Anybody can answer The best answers are voted up and rise to the top device mapper on RHEL6 unable to create devs for LVM logical volume up vote 3 down vote favorite I have XEN guest running RHEL6, and it has a LUN presented from the Dom0. This contains an LVM volume groups called vg_ALHINT (INT for Integration and ALH is an abbreviation of its Oracle database name). The data is Oracle 11g. The VG was imported, activated and udev created the maps for each logical volume. However device mapper did not create mappings for one of the logical volumes [LV], and for the LV in question it created /dev/dm-2 with different major minor number compared to the rest of LVs. # dmsetup table vg_ALHINT-arch: 0 4300800 linear 202:16 46139392 vg0-lv6: 0 20971520 linear 202:2 30869504 vg_ALHINT-safeset2: 0 4194304 linear 202:16 35653632 vg0-lv5: 0 2097152 linear 202:2 28772352 vg_ALHINT-safeset1: 0 4186112 linear 202:16 54528000 vg0-lv4: 0 524288 linear 202:2 28248064 vg0-lv3: 0 4194304 linear 202:2 24053760 vg_ALHINT-oradata: ** vg0-lv2: 0 4194304 linear 202:2 19859456 vg0-lv1: 0 2097152 linear 202:2 17762304 vg0-lv0: 0 17760256 linear 202:2 2048 vg_ALHINT-admin: 0 4194304 linear 202:16 41945088 ** You can see above vg_ALHINT-oradata is empty. # ls -l /dev/mapper/ total 0 [root@iui-alhdb01 ~]# ls -l /dev/mapper/ total 0 crw-rw---- 1 root root 10, 58 Apr 3 13:43 control lrwxrwxrwx 1 root root 7 Apr 3 13:43 vg0-lv0 -> ../dm-0 lrwxrwxrwx 1 root root 7 Apr 3 13:43 vg0-lv1 -> ../dm-1 lrwxrwxrwx 1 root root 7 Apr 3 14:35 vg0-lv2 -> ../dm-2 lrwxrwxrwx 1 root root 7 Apr 3 13:43 vg0-lv3 -> ../dm-3 lrwxrwxrwx 1 root root 7 Apr 3 13:43 vg0-lv4 -> ../dm-4 lrwxrwxrwx 1 root root 7 Apr 3 13:43 vg0-lv5 -> ../dm-5 lrwxrwxrwx 1 root root 7 Apr 3 13:43 vg0-lv6 -> ../dm-6 lrwxrwxrwx 1 root root 7 Apr 3 13:59 vg_ALHINT-admin -> ../dm-8 lrwxrwxrwx 1 root root 7 Apr 3 13:59 vg_ALHINT-arch -> ../dm-9 brw-rw---- 1 root di