This bug has been copied from bug #608109 and has been proposed to be backported to 5.5 z-stream (EUS).
Hello Red Hat: Is the patch code for the Spinning up disk issue upstream? If so, can you give us a name and pointer to it? Thanks!
On Fri, Feb 20, 2009 at 12:03:58PM +0000, Rengarajan, Narayanan (STSD) wrote: Spinning up disk is observed on standby paths until timeout, resulting in longer path restoration time in 2.6.27 kernel. Steps to reproduce: 1. present a standby lun to the host 2. do a discovery from the host (scan the scsi bus) 3. Spinning of disks is observed in /var/log/messages Whenever a device goes offline and comes back, the new sd device takes longer time to get created. This is because of the spinning up of disk in sd_spinup_disk fuction as the standby paths would return device not ready with 0x04/0x0b asc/ascq. Commit id from storage-tree: 3dd6f92a1a7ad85c54d47fd9d73371a32c0bde4 If you need me to look up the pointer, let me know.
Hi Rob, Yes, looking up the pointer would be good. Thanks!!
http://git.kernel.org/?p=linux/kernel/git/jejb/scsi-misc-2.6.git;a=commit;h=33dd6f92a1a7ad85c54d47fd9d73371a32c0bde4
in kernel 2.6.18-194.20.1.el5 linux-2.6-scsi-fix-disk-spinup-for-shorter-path-restore-times.patch
An advisory has been issued which should help the problem described in this bug report. This report is therefore being closed with a resolution of ERRATA. For more information on therefore solution and/or where to find the updated files, please follow the link below. You may reopen this bug report if the solution does not work for you. http://rhn.redhat.com/errata/RHSA-2010-0839.html
Technical note added. If any revisions are required, please edit the "Technical Notes" field accordingly. All revisions will be proofread by the Engineering Content Services team. New Contents: Previously, disks were spinning up for devices in an Active/Passive array on standby path side. This caused long boot up times which resulted in SD devices to be all created before multipath was ready. With this update, a disk is not spun up if returning NOT_READY on standby path.