NetBSD Problem Report #7560

Received: (qmail 17062 invoked from network); 12 May 1999 06:26:55 -0000
Message-Id: <199905120624.QAA04422@balrog.supp.cpr.itg.telecom.com.au>
Date: Wed, 12 May 1999 16:24:16 +1000
From: simonb@netbsd.org
Reply-To: simonb@netbsd.org
To: gnats-bugs@gnats.netbsd.org
Subject: pax problem with NFS installs
X-Send-Pr-Version: 3.95

>Number:         7560
>Category:       install
>Synopsis:       pax problem with NFS installs
>Confidential:   no
>Severity:       serious
>Priority:       high
>Responsible:    install-manager
>State:          closed
>Class:          sw-bug
>Submitter-Id:   net
>Arrival-Date:   Tue May 11 23:35:01 +0000 1999
>Closed-Date:    Mon Dec 18 05:11:34 +0000 2000
>Last-Modified:  Mon Dec 18 05:11:34 +0000 2000
>Originator:     Simon Burge
>Release:        1.4
>Organization:
	TNF
>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?
>Release-Note:
>Audit-Trail:

From: Andrew Brown <atatat@atatdot.net>
To: simonb@netbsd.org
Cc: gnats-bugs@gnats.netbsd.org
Subject: Re: install/7560: pax problem with NFS installs
Date: Wed, 12 May 1999 10:00:00 -0400

 >>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?

 tar --exclude '.nfs*'

 ??  :)

 -- 
 |-----< "CODE WARRIOR" >-----|
 codewarrior@daemon.org             * "ah!  i see you have the internet
 twofsonet@graffiti.com (Andrew Brown)                that goes *ping*!"
 andrew@crossbar.com       * "information is power -- share the wealth."
Responsible-Changed-From-To: gnats-admin->install-manager 
Responsible-Changed-By: fair 
Responsible-Changed-When: Thu Jun 17 13:57:53 PDT 1999 
Responsible-Changed-Why:  
This PR is the responsibility of the NetBSD install bug manager, 
not the GNATS database administrator. 
State-Changed-From-To: open->closed 
State-Changed-By: hubertf 
State-Changed-When: Sun Dec 17 21:10:18 PST 2000 
State-Changed-Why:  

This problem was fixed some time ago: 

src/bin/pax/tables.c: 
date: 2000/03/21 02:15:24;  author: thorpej;  state: Exp;  lines: +57 -2 



- Hubert 

P.S.: That's rev. 1.13 above (bad editor here...) 
>Unformatted:

NetBSD Home
NetBSD PR Database Search

(Contact us) $NetBSD: query-full-pr,v 1.51 2026/08/10 02:28:17 riastradh Exp $
$NetBSD: gnats_config.sh,v 1.10 2026/05/13 22:00:09 riastradh Exp $
Copyright © 1994-2026 The NetBSD Foundation, Inc. ALL RIGHTS RESERVED.