Bug 103179

Summary:	NFS client has empty dirs
Product:	Red Hat Enterprise Linux 3	Reporter:	Elliot Lee <sopwith>
Component:	kernel	Assignee:	Steve Dickson <steved>
Status:	CLOSED CURRENTRELEASE	QA Contact:	Brian Brock <bbrock>
Severity:	medium	Docs Contact:
Priority:	medium
Version:	3.0	CC:	alexl, kambiz, riel
Target Milestone:	---
Target Release:	---
Hardware:	All
OS:	Linux
Whiteboard:
Fixed In Version:		Doc Type:	Bug Fix
Doc Text:		Story Points:	---
Clone Of:		Environment:
Last Closed:	2004-08-03 09:47:16 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:

Description Elliot Lee 2003-08-27 12:37:38 UTC

On ppc64 (411) and ia64 (382) directories sometimes appear to be empty even when
they are not. Touching a file inside the 'empty' directory makes the full
contents appear.

Comment 1 Steve Dickson 2003-08-27 12:42:16 UTC

What are the steps to reproduce this problem....

Comment 2 Elliot Lee 2003-08-27 12:50:38 UTC

Run a complete beehive installation?

I haven't the foggiest.

The basic set of operations that causes the path to come into existence are:

1. Populate directory while it is at a different path
2. Move parent directory to a new location.

e.g.


mkdir -p /tmp/foo/ppc64 # On the NFS server box
# On an NFS client box, not necessarily the one where the problem shows up
echo blah > /tmp/foo/ppc64/dummy.txt
mv /tmp/foo /tmp/blah # On the NFS server box

ls /tmp/blah/ppc64 # On the NFS client box in question, should show files but doesn't

Comment 3 Steve Dickson 2003-08-27 20:07:52 UTC

There is nfs.o on cur81 in /tmp that I would you to try....

Comment 8 Steve Dickson 2004-08-03 09:47:16 UTC

Since I not heard about this happen in later releases,
I'm going to assume its fixed. Please reopen if this
is not the case....