PDA

View Full Version : multipath.conf for FCP LUN SLES10 SP3



gso_linux
04-May-2012, 22:00
Hello,

I would kindly ask someone if you could check my multipath.conf file, I have used this file for my SLES10SP3 Server with FCP attached LUNs, NetApp Metrocluster. But after takeover and giveback the filesystems created on these LUNs become read-only.

multipath-tools-0.4.7-34.56.1
kernel-smp-2.6.16.60-0.77.1
The part after device is looking like this

vendor "NETAPP"
product "LUN"
getuid_callout "/sbin/scsi_id -g -u -s /block/%n"
prio_callout "/sbin/mpath_prio_alua /dev/%n"
prio "alua"
features "1 queue_if_no_path"
hardware_handler "0"
path_grouping_policy group_by_prio
failback immediate
rr_weight uniform
rr_min_io 128
path_checker tur


Thank you in advance for your tips and contributions.

Automatic reply
10-May-2012, 13:30
gso,

It appears that in the past few days you have not received a response to your
posting. That concerns us, and has triggered this automated reply.

Has your issue been resolved? If not, you might try one of the following options:

- Visit http://www.suse.com/support and search the knowledgebase and/or check all
the other support options available.
- You could also try posting your message again. Make sure it is posted in the
correct newsgroup. (http://forums.suse.com)

Be sure to read the forum FAQ about what to expect in the way of responses:
http://forums.suse.com/faq.php

If this is a reply to a duplicate posting, please ignore and accept our apologies
and rest assured we will issue a stern reprimand to our posting bot.

Good luck!

Your SUSE Forums Team
http://forums.suse.com

Magic31
14-May-2012, 08:51
Hello,

I would kindly ask someone if you could check my multipath.conf file, I have used this file for my SLES10SP3 Server with FCP attached LUNs, NetApp Metrocluster. But after takeover and giveback the filesystems created on these LUNs become read-only.

multipath-tools-0.4.7-34.56.1
kernel-smp-2.6.16.60-0.77.1
The part after device is looking like this

vendor "NETAPP"
product "LUN"
getuid_callout "/sbin/scsi_id -g -u -s /block/%n"
prio_callout "/sbin/mpath_prio_alua /dev/%n"
prio "alua"
features "1 queue_if_no_path"
hardware_handler "0"
path_grouping_policy group_by_prio
failback immediate
rr_weight uniform
rr_min_io 128
path_checker tur


Thank you in advance for your tips and contributions.

As I normally do setups for EMC and Equallogic SAN's.. I don't have personal experience with NetApp's on SLES.

A quick look in the multipath.conf.defaults on a SLES 11 SP1 system I have running here shows some differences in multipath.conf section for the NETAPP:



# device {
# vendor "NETAPP"
# product "LUN.*"
# getuid_callout "/lib/udev/scsi_id --whitelisted --device=/dev/%n"
# features "1 queue_if_no_path"
# hardware_handler "0"
# path_selector "round-robin 0"
# path_grouping_policy group_by_prio
# failback immediate
# rr_weight uniform
# rr_min_io 128
# path_checker directio
# prio netapp
# }


I'm curious how you got to your multipath.conf (following a NetApp doc for example)? The path_checker parameter could be one to check (take care when changing these params with running production installations).
Note that the multipath.conf.defaults are normally a generic starting point and not always optimized... So always double check with the SAN vendor given guidelines and setup as the correct parameters also can depend on with settings have been configured within your SAN.

Also, could you post the output of 'multipath -ll'?

Cheers,
Willem