Hello.
I have two systems that are identical hardware excepting local disks and processors. I am trying to setup multipath to map to an EMC san via fiber channel. Running 'apt-get install multipath-tools and multipath-tools-boot' runs on both with no problem. After doing this, one system has no issue booting and multipath reports no targets (using the standard blacklist to omit local disks and what not). The other system gives two alternating issues at boot. One is fatal, the other not so fatal but requires user intervention.
The fatal issue occurs during boot and happens during the device-mapper loading and reports errors 'ioctl: error adding target to table' and 'dm-linear: Device lookup failed'. It then throws errors trying to run /scripts/local-premount indicating 'No such device'. Ultimately halting in (initramfs).
Rebooting the same system (doing a soft reset) will then not throw that error, but get down to the point of running file system checks and throw and issue stating "Device or resource busy while trying to open /dev/sda1 File system mounted or opened exclusively by another program?" I then can hit CTRL-D to continue booting and system boots. After this boot, running multipath -ll shows (that wwid is for the local disk):
3600508e000000000135b45d76b4e4805dm-0 ,
[size=74G][features=0][hwhandler=0]
\_ round-robin 0 [prio=-1][active]
\_ #:#:#:# - #:# [active][undef]
Whereas the other system shows no information with the same command.
It would appear as there is some conflict with multipath locking the local disk and competing with LVM or something of that nature.
Any ideas? I have tried blacklisting the local device which it would appear to be doing ... but the output is different.
System with issues 'multipath -v3' shows (I blacklisted all /dev/sda* to see if that made a difference (which it did not)):
pxsodhq1:~# multipath -v3
loop0: device node name blacklisted
loop1: device node name blacklisted
loop2: device node name blacklisted
loop3: device node name blacklisted
loop4: device node name blacklisted
loop5: device node name blacklisted
loop6: device node name blacklisted
loop7: device node name blacklisted
sr0: device node name blacklisted
sda: device node name blacklisted
dm-0: device node name blacklisted
dm-2: device node name blacklisted
dm-3: device node name blacklisted
dm-4: device node name blacklisted
dm-5: device node name blacklisted
===== no paths =====
params = 0 0 1 1 round-robin 0 1 1 8:0 1000
status = 2 0 0 0 1 1 A 0 1 0 8:0 A 0
8:0: not found in pathvec
: mask = 0x1f
: no 'dev' attribute in sysfs
:
) wwid blacklisted
I have two systems that are identical hardware excepting local disks and processors. I am trying to setup multipath to map to an EMC san via fiber channel. Running 'apt-get install multipath-tools and multipath-tools-boot' runs on both with no problem. After doing this, one system has no issue booting and multipath reports no targets (using the standard blacklist to omit local disks and what not). The other system gives two alternating issues at boot. One is fatal, the other not so fatal but requires user intervention.
The fatal issue occurs during boot and happens during the device-mapper loading and reports errors 'ioctl: error adding target to table' and 'dm-linear: Device lookup failed'. It then throws errors trying to run /scripts/local-premount indicating 'No such device'. Ultimately halting in (initramfs).
Rebooting the same system (doing a soft reset) will then not throw that error, but get down to the point of running file system checks and throw and issue stating "Device or resource busy while trying to open /dev/sda1 File system mounted or opened exclusively by another program?" I then can hit CTRL-D to continue booting and system boots. After this boot, running multipath -ll shows (that wwid is for the local disk):
3600508e000000000135b45d76b4e4805dm-0 ,
[size=74G][features=0][hwhandler=0]
\_ round-robin 0 [prio=-1][active]
\_ #:#:#:# - #:# [active][undef]
Whereas the other system shows no information with the same command.
It would appear as there is some conflict with multipath locking the local disk and competing with LVM or something of that nature.
Any ideas? I have tried blacklisting the local device which it would appear to be doing ... but the output is different.
System with issues 'multipath -v3' shows (I blacklisted all /dev/sda* to see if that made a difference (which it did not)):
pxsodhq1:~# multipath -v3
loop0: device node name blacklisted
loop1: device node name blacklisted
loop2: device node name blacklisted
loop3: device node name blacklisted
loop4: device node name blacklisted
loop5: device node name blacklisted
loop6: device node name blacklisted
loop7: device node name blacklisted
sr0: device node name blacklisted
sda: device node name blacklisted
dm-0: device node name blacklisted
dm-2: device node name blacklisted
dm-3: device node name blacklisted
dm-4: device node name blacklisted
dm-5: device node name blacklisted
===== no paths =====
params = 0 0 1 1 round-robin 0 1 1 8:0 1000
status = 2 0 0 0 1 1 A 0 1 0 8:0 A 0
8:0: not found in pathvec
: mask = 0x1f
: no 'dev' attribute in sysfs
:
) wwid blacklisted