Bug 2090 – nfs creates a directory that it can't use from Solaris

Bug 2090 - nfs creates a directory that it can't use from Solaris

Summary:	nfs creates a directory that it can't use from Solaris

Status:	CLOSED WONTFIX

Aliases:	None

Product:	Red Hat Linux
Classification:	Retired
Component:	nfs-server (Show other bugs)
Sub Component:
Version:	5.2
Hardware:	i386 Linux

Priority	high Severity high
Target Milestone:	---
Target Release:	---
Assigned To:	Michael K. Johnson
QA Contact:
Docs Contact:

URL:
Whiteboard:
Keywords:

Depends On:
Blocks:
	Show dependency tree / graph

Reported:	1999-04-09 12:59 EDT by markw
Modified:	2008-05-01 11:37 EDT (History)
CC List:	1 user (show)

See Also:
Fixed In Version:
Doc Type:	Bug Fix
Doc Text:
Story Points:	---
Clone Of:
Environment:
Last Closed:	2002-12-14 23:13:35 EST
Type:	---
Regression:	---
Mount Type:	---
Documentation:	---
CRM:
Verified Versions:
Category:	---
oVirt Team:	---
RHEL 7.3 requirements from Atomic Host:
Cloudforms Team:	---

Attachments	(Terms of Use)
Add an attachment (proposed patch, testcase, etc.)

Groups: None (edit)

Description markw 1999-04-09 12:59:06 EDT

It seems that if, in rapid succession, if one creates a
file, then deletes it, then creates a directory, the
directory receives the same inode as the deleted file. The
file information is still cached, and nfs does not see it as
a directory. ls does, list it as a dir most of the time.

This happens on RedHat Linux 5.1 and 5.2, and 5.2 with
kernel nfs. The clients are Solaris and Digital UNIX.

Comment 1 Alan Cox 2002-12-14 23:13:35 EST

unfsd is expired and gone

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