Bug 703610

Ben: I'm putting this in needinfo to ask what is new for RHEL 5.7 for dm multipath.

Do you have an annotated configuration file I could check through?

This request was evaluated by Red Hat Product Management for
inclusion in the current release of Red Hat Enterprise Linux.
Because the affected component is not scheduled to be updated in the
current release, Red Hat is unfortunately unable to address this
request at this time. Red Hat invites you to ask your support
representative to propose this request, if appropriate and relevant,
in the next release of Red Hat Enterprise Linux.

Here are the new parameters. They only exist in the defaults section of multipath.conf

#
#      #
#      # name    : fast_io_fail_tmo
#      # scope   : multipath & multipathd
#      # desc    : The number of seconds the scsi layer will wait after a
#      #           problem has been detected on a FC remote port before failing
#      #           IO to devices on that remote port.
#      # values  : off | n >= 0 (smaller than dev_loss_tmo)
#      # default : determined by the OS
#      fast_io_fail_tmo 5
#
#      #
#      # name    : dev_loss_tmo
#      # scope   : multipath & multipathd
#      # desc    : The number of seconds the scsi layer will wait after a
#      #           problem has been detected on a FC remote port before
#      #           removing it from the system.
#      # values  : n > 0
#      # default : determined by the OS
#      dev_loss_tmo 600
#
#      #
#      # name    : file_timeout
#      # scope   : multipath & mutipathd
#      # desc    : The number of seconds multipath will wait for a necessary
#      #           file to appear, while setting up a multipath device.
#      # values  : n > 0
#      # default : 90
#      file_timeout 120
#

The only other new features is support for a couple of new HP Arrays.

Ben:

Does the file_timeout value exist in the devices section as well?  Or is that limited to the defaults section?

-Steven

Ben:

Another question:

The RHEL 5 document says this:

An annotated version of the configuration file can be found in
/usr/share/doc/device-mapper-multipathd-0.4.7/multipath.conf.annotated

I have a RHEL 5 test system I built a few weeks ago, and that path is correct, but the file on my system does not include the file_timeout value. Is there a later version -- in other words, is that path correct for RHEL 5.7?

-Steven

Ben has answered these questions in email:

>> Does the file_timeout value exist in the devices section as well?  Or is that
>> >> limited to the defaults section?
Yes. That is a defaults only parameter.

> >
> > and
> >
> >
>> >> The RHEL 5 document says this:
>> >>
>> >> An annotated version of the configuration file can be found in
>> >> /usr/share/doc/device-mapper-multipathd-0.4.7/multipath.conf.annotated
>> >>
>> >> I have a RHEL 5 test system I built a few weeks ago, and that path is correct,
>> >> but the file on my system does not include the file_timeout value. Is there a
>> >> later version -- in other words, is that path correct for RHEL 5.7?
That path is correct. It's possible that the most recent RHEL 5.7
package doesn't include all of the multipath.conf.annotated updates.

-----

I have rebuilt the document and when it appears on the Brew staging area I will put this BZ into ON_QA.

Ben: I've sent email about this, but I'm marking this BZ as NEEDINFO from you with a deadline of tomorrow because I need quick verification of something.

The QA reviewer noted that in the table of configuration file defaults I say this:

getuid_callout
Specifies the default program and arguments to call out to obtain a unique path identifier. An absolute path is required. The default value is /sbin/scsi_id -g -u -s.

But he points this out:

[bug] I have device-mapper-multipath-0.4.7-42.el5_6.3.x86_64 installed and according to
/usr/share/doc/device-mapper-multipath-0.4.7/multipath.conf.annotated the default value is /sbin/scsi_id -g -u -s /block/%n 

Do I need to add that /block/%n to the default value for getuid_callout?

-Steven

Removing the NEEDINFO from Ben, who has provided the info in email.