Bug 63033 - Stale file handles on unplanned NFS failover
Summary: Stale file handles on unplanned NFS failover
Keywords:
Status: CLOSED ERRATA
Alias: None
Product: Red Hat Enterprise Linux 2.1
Classification: Red Hat
Component: clumanager
Version: 2.1
Hardware: All
OS: Linux
medium
medium
Target Milestone: ---
Assignee: Lon Hohberger
QA Contact:
URL:
Whiteboard:
Depends On: 63162 70115 70132
Blocks:
TreeView+ depends on / blocked
 
Reported: 2002-04-09 15:13 UTC by Tim Burke
Modified: 2008-05-01 15:38 UTC (History)
0 users

Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Clone Of:
Environment:
Last Closed: 2002-06-13 18:40:26 UTC
Target Upstream Version:
Embargoed:


Attachments (Terms of Use)


Links
System ID Private Priority Status Summary Last Updated
Red Hat Product Errata RHBA-2002:226 0 normal SHIPPED_LIVE Fixes for clumanager addressing starvation and service hangs 2002-10-08 04:00:00 UTC

Description Tim Burke 2002-04-09 15:13:08 UTC
From Bugzilla Helper:
User-Agent: Mozilla/4.78 [en] (X11; U; Linux 2.4.7-10 i686)

Description of problem:
clumanager-1.0.9

During the recent cluster training, we setup an NFS service.  Then client mounts
were setup to run scripts which were tar-ing on/off this nfs mount.

Performing service relocations seemed to work fine.  However if we power cycled
the cluster member serving the cluster service, in about 1/3 of the cases the
client would encounter stale file handles.  When this happened the only remedy
from the client's perspective was to manually remount.



Version-Release number of selected component (if applicable):


How reproducible:
Sometimes

Steps to Reproduce:
1.Setup nfs service
2.mount on client, initiate exercisers on client (e.g. tar)
3.power off active nfs server cluster member
	

Actual Results:  About 1/3 of the time nfs stale file handles occurred.

Expected Results:  Transparent failover.

Additional info:

Comment 1 Lon Hohberger 2002-05-13 17:26:11 UTC
Fix in pool.  Awaiting testing from different developers before closing.


Note You need to log in before you can comment on or make changes to this bug.