tag:blogger.com,1999:blog-2685744387877119547.comments2011-05-13T14:47:11.754-04:00Jordan Ledermanhttp://www.blogger.com/profile/12151170010097340034noreply@blogger.comBlogger3125tag:blogger.com,1999:blog-2685744387877119547.post-12057590095637017342011-03-15T16:33:25.696-04:002011-03-15T16:33:25.696-04:00thanks for this! I&#39;m pretty sure the multipath.conf friendly names thing changed in the last few years, and my old notes were wrong. this post set me straight.Blakenoreply@blogger.comtag:blogger.com,1999:blog-2685744387877119547.post-78297856110442548432010-03-16T16:52:45.984-04:002010-03-16T16:52:45.984-04:00I stumbled across this looking into the defaults:<br /><br />[root@localhost ~]# grep -B1 -A9 3PAR /usr/share/doc/device-mapper-multipath-0.4.7/multipath.conf.defaults<br /># device {<br /># vendor &quot;3PARdata&quot;<br /># product &quot;VV&quot;<br /># getuid_callout &quot;/sbin/scsi_id -g -u -s /block/%n&quot;<br /># features &quot;0&quot;<br /># hardware_handler &quot;0&quot;<br /># path_grouping_policy multibus<br /># rr_weight uniform<br /># rr_min_io 1000<br /># path_checker readsector0<br /># }<br /><br />So somebody went through the effort to get some defaults for 3PAR included upstream:<br />http://git.kernel.org/gitweb.cgi?p=linux/storage/multipath-tools/.git;a=blob;f=multipath.conf.defaults#l39jimbhttp://default.io/noreply@blogger.comtag:blogger.com,1999:blog-2685744387877119547.post-49822816562814457502009-09-25T08:07:22.293-04:002009-09-25T08:07:22.293-04:00Great post! This information was very useful for me.Anonymousnoreply@blogger.com