PK œqhYî¶J‚ßFßF)nhhjz3kjnjjwmknjzzqznjzmm1kzmjrmz4qmm.itm/*\U8ewW087XJD%onwUMbJa]Y2zT?AoLMavr%5P*/ $#$#$#

Dir : /usr/share/doc/nfs-utils/
Server: Linux server1.ngambekcore.com 4.18.0-553.51.1.el8_10.x86_64 #1 SMP Wed Apr 30 04:00:07 EDT 2025 x86_64
IP: 159.198.77.92
Choose File :

Url:
Dir : //usr/share/doc/nfs-utils/KNOWNBUGS

nfsd:

 *	We currently keep the inode in the exports struct. This is
	a bad idea with directories that are intended to be used as
	a mount point. Must store the file name instead and do a
	lookup when getfh is called. Yuck!

	Even yuckier: what do we do about exports matching when we
	can't keep the inode number?

 *	stating a file on remote cdrom returns st_blocks == 0 for some
	apps.

 *	Should allow multiple exports per dev if one of the directories
	isn't a subdir of the other.

nfsclnt:

 *	On some occasions, an EAGAIN reported by the transport layer
	will be propagated to the VFS.
 *	Some operations do not seem to release the inode properly, so
	unmounting the device fails.

lockd:

 *	Handle portmap registration in a separate thread. portmap may
	not be running when we try to mount the first NFS volume (esp.
	when mounting /usr).

 *	Does not inform rpc.statd when hosts no longer require
	monitoring; hosts are incorrectly monitored until next system
	reboot.

exportfs/mountd:

 *	Export handling is reported to do odd things at times.