No relevant resource is found in the selected language.

This site uses cookies. By continuing to browse the site you are agreeing to our use of cookies. Read our privacy policy>Search


To have a better experience, please upgrade your IE browser.


not reseting after installing multipathing lead to cannot read and write LV device because of LVM visit path not clean

Publication Date:  2012-09-20 Views:  76 Downloads:  0
Issue Description
Map S2600 to a HP host, beforetime user establish LV and read write operation without multipathing software. Now install multipathing software, but it cannot read write inhere LV. Then uninstall multipathing software, it is still, operation is cut.
Alarm Information
Handling Process
Modify /etc/lvm/.cache to .cache~ and pvscan physical volume again. Run fdisk –l ,and there is not Input/Output error.
Root Cause
Run fdisk –l. It shows dev/dm-0 and /dev/dm-1 Input/Output error. dm-0 and dm-1 cannot be visited. Read write other disks fdisk –l listed is normal. Physical link via lsscsi is twice as many as fdisk –l. physical link is normal and IO can access storage.
     Physical link and volume is good , why cannot read write LV?  The reason is that LV gets lvm path from lvm cache, but cache path become virtual path after installing mutipating. There is two solutions. For one, reset host, pvscan will get new path. For another, delete /etc/lvm/.cache document, pvscan will get new path.
Install mutipathing first , then establish PV, VG and LV.