Since I see the following entry at /usr/share/doc/device-mapper-multipath-0.4.7/multipath.conf.defaults I am assuming I do not need to add it to multipath.conf but I do not know exaclty. Also my storage is Hitachi openv and the default one has Product name as "DF.*" as you can see below.
So I am confused in here.
device { # vendor "HITACHI" # product "DF.*" # getuid_callout "/sbin/scsi_id -g -u -s /block/%n" # prio_callout "/sbin/mpath_prio_hds_modular %d" # features "0" # hardware_handler "0" # path_grouping_policy group_by_prio # failback immediate # rr_weight uniform # rr_min_io 1000 # path_checker readsector0 # }
Thanks Paras.
On Fri, Jan 8, 2010 at 9:39 AM, Ray Van Dolson rayvd@bludgeon.org wrote:
On Fri, Jan 08, 2010 at 09:37:25AM -0600, Paras pradhan wrote:
Per,
Yes I have a device mapper out of my detected LUNS. My storage is Hitachi OpenV . My multipath.conf files looks like below. Do I need to add
anything
to it since failover is not working. When I unplugg the cable in the 1st port of my HBA... my server reboots and I don't know what is causing this reboot. And after reboot when I plug the cable back, no recovery is done
and
to make it work I have to reboot the server once again with cable
plugged.
-- blacklist { devnode "^sda" }
defaults { user_friendly_names yes failback immediate }
Seems like you need a devices {} section to define how multipathd interacts with your storage, identifies problems and chooses a path to use...
Ray _______________________________________________ CentOS mailing list CentOS@centos.org http://lists.centos.org/mailman/listinfo/centos