>Number:         7560
>Category:       install
>Synopsis:       pax problem with NFS installs
>Confidential:   no
>Severity:       serious
>Priority:       high
>Responsible:    gnats-admin (GNATS administrator)
>State:          open
>Class:          sw-bug
>Submitter-Id:   net
>Arrival-Date:   Tue May 11 23:35:01 1999
>Last-Modified:
>Originator:     Simon Burge
>Organization:
	TNF
>Release:        NetBSD 1.4
>Environment:
	NetBSD mona 1.4 NetBSD 1.4 (GENERIC) #32: Fri May  7 19:15:34 EST 1999
	root@mona:/usr/src/sys/arch/pmax/compile/GENERIC pmax

>Description:
	During an install from a diskless NFS root filesystem onto a
	local disk, sysinst calls pax(1) to copy the contents of the
	diskless root filesystem to the newly newfs'd root filesystem
	with the command "pax -X -r -w -pe / /mnt", and then files
	with an error like "File /tmp/.nfsA00a34 changed size during
	copy to /mnt/tmp/.nfsA00a34".

	Pax creates a file in /tmp and then unlink()s it and stores the
	file permissions in there.  Unfortunately in an NFS environment,
	this leaves a .nfs file lying around until after it's closed.

>How-To-Repeat:
	Run sysinst from an NFS install on a pmax.

>Fix:
	None given.  Using GNU tar(1) is not the right answer :-)
	Maybe an option to pax(1) to keep the file time database
	in core instead of on disk, or keep the database in core
	until it reaches a certain size?
>Audit-Trail:
>Unformatted: