Bug 656004

Summary: [NetApp 6.1 bug] Disable lpfc heartbeat by default in RHEL6
Product: Red Hat Enterprise Linux 6 Reporter: Martin George <marting>
Component: kernelAssignee: Rob Evers <revers>
Status: CLOSED DUPLICATE QA Contact: Red Hat Kernel QE team <kernel-qe>
Severity: high Docs Contact:
Priority: high    
Version: 6.1CC: andriusb, coughlan, dhoward, jwest, revers, xdl-redhat-bugzilla
Target Milestone: rcKeywords: OtherQA
Target Release: 6.1   
Hardware: Unspecified   
OS: Unspecified   
Whiteboard:
Fixed In Version: Doc Type: Bug Fix
Doc Text:
Story Points: ---
Clone Of: Environment:
Last Closed: 2010-12-02 22:16:15 UTC Type: ---
Regression: --- Mount Type: ---
Documentation: --- CRM:
Verified Versions: Category: ---
oVirt Team: --- RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: --- Target Upstream Version:
Embargoed:
Attachments:
Description Flags
patch do disable heartbeats by default for rhel6.1 as provided by Emulex. none

Description Martin George 2010-11-22 20:31:42 UTC 
Description of problem:

The heartbeat setting in RHEL6 lpfc (lpfc_enable_hba_heartbeat) is enabled by default. This is known to trigger issues wherein the Emulex FC ports sometimes get offlined during IO - refer bug 599487 for details.

So to avoid hitting this, it is now recommended to disable the lpfc heartbeat by setting lpfc_enable_hba_heartbeat=0. This should now be made the default setting in RHEL6 going forward.
Comment 2 Andrius Benokraitis 2010-12-02 18:42:43 UTC 
Rob, can you attach a RHEL 6 patch, even if it is the same as what's in :

https://bugzilla.redhat.com/show_bug.cgi?id=599487#c59

Thanks!
Comment 3 Andrius Benokraitis 2010-12-02 18:43:09 UTC 
Requesting this for 6.0.z, since the same patch is already queued up for 5.5.z.
Comment 4 Rob Evers 2010-12-02 20:18:49 UTC 
Created attachment 464357 [details]
patch do disable heartbeats by default for rhel6.1 as provided by Emulex.
Comment 7 Rob Evers 2010-12-02 22:16:15 UTC 
See:

https://bugzilla.redhat.com/show_bug.cgi?id=655935#c6

*** This bug has been marked as a duplicate of bug 655935 ***