Re: iscsi multipath failure with libvirtError: Failed to open file '/dev/mapper/Mar': No such file or directory
On Mon, Mar 23, 2015 at 10:14:31PM +0530, mad Engineer wrote:
hello All,
I know the issue is related to libvirt,but i dont know
where to ask.
The libvirt mailing list is the place to ask libvirt questions. I have
CCed it.
i have centos 6.6 running KVM as compute node in openstack icehouse
when i try to attach volume to instance it shows
2596: error : virStorageFileGetMetadataRecurse:952 : Failed to open
file '/dev/mapper/Mar': No such file or directory
in libvirt log
This does not always happen when it happens no one will be able to
attach volume to instance
using EMC VNX as storage backend.
multipath.conf
# Skip the files uner /dev that are definitely not FC/iSCSI devices
# Different system may need different customization
devnode ^(ram|raw|loop|fd|md|dm-|sr|scd|st)[0-9]*
devnode ^hd[a-z][0-9]*
devnode ^cciss!c[0-9]d[0-9]*[p[0-9]*]
# Skip LUNZ device from VNX
device {
vendor DGC
product LUNZ
}
}
defaults {
user_friendly_names no
flush_on_last_del yes
}
devices {
# Device attributed for EMC CLARiiON and VNX series ALUA
device {
vendor DGC
product .*
product_blacklist LUNZ
path_grouping_policy group_by_prio
path_selector round-robin 0
path_checker emc_clariion
features 1 queue_if_no_path
hardware_handler 1 alua
prio alua
failback immediate
}
}
Can any one help me with this issue
You may need to check dmesg or logs related to the EMC storage. In
particular, check for LUNs going offline, coming online, or the
multipath device changing state.
Stefan
pgpM6PeZXrDpl.pgp
Description: PGP signature
iscsi multipath failure with libvirtError: Failed to open file '/dev/mapper/Mar': No such file or directory
hello All,
I know the issue is related to libvirt,but i dont know
where to ask.
i have centos 6.6 running KVM as compute node in openstack icehouse
when i try to attach volume to instance it shows
2596: error : virStorageFileGetMetadataRecurse:952 : Failed to open
file '/dev/mapper/Mar': No such file or directory
in libvirt log
This does not always happen when it happens no one will be able to
attach volume to instance
using EMC VNX as storage backend.
multipath.conf
# Skip the files uner /dev that are definitely not FC/iSCSI devices
# Different system may need different customization
devnode ^(ram|raw|loop|fd|md|dm-|sr|scd|st)[0-9]*
devnode ^hd[a-z][0-9]*
devnode ^cciss!c[0-9]d[0-9]*[p[0-9]*]
# Skip LUNZ device from VNX
device {
vendor DGC
product LUNZ
}
}
defaults {
user_friendly_names no
flush_on_last_del yes
}
devices {
# Device attributed for EMC CLARiiON and VNX series ALUA
device {
vendor DGC
product .*
product_blacklist LUNZ
path_grouping_policy group_by_prio
path_selector round-robin 0
path_checker emc_clariion
features 1 queue_if_no_path
hardware_handler 1 alua
prio alua
failback immediate
}
}
Can any one help me with this issue
--
To unsubscribe from this list: send the line unsubscribe kvm in
the body of a message to majord...@vger.kernel.org
More majordomo info at http://vger.kernel.org/majordomo-info.html
