Thanks for the Link Ray.
One thing I am confused is... "failover manual" means whenever there is a link failure this will case the host to be rebooted?
Paras.
On Fri, Jan 8, 2010 at 9:53 AM, Ray Van Dolson rayvd@bludgeon.org wrote:
On Fri, Jan 08, 2010 at 09:45:14AM -0600, Paras pradhan wrote:
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 # }
I'm not familiar with this SAN, so can't suggest to you a better device configuration snippet.
Google may help you out: search for your device type and "multipath.conf". Alternately, if your vendor supports RHEL5 (I'm sure they do), you could contact them and ask them to provide you with a known good configuration.
Actually, a quick search yields this:
http://www.calivia.com/book/export/html/74
Which seems to have what you need (verify of course).
Ray _______________________________________________ CentOS mailing list CentOS@centos.org http://lists.centos.org/mailman/listinfo/centos