Bug 21540

Summary:	installworld panics for diskless clients
Product:	Base System	Reporter:	Sean O'Connell <sto>
Component:	conf	Assignee:	Boris Popov <bp>
Status:	Closed FIXED
Severity:	Affects Only Me
Priority:	Normal
Version:	4.1-STABLE
Hardware:	Any
OS:	Any

Description Sean O'Connell 2000-09-25 18:30:01 UTC

	Now that make installworld, uses copies the install target
	binaries into /tmp/inst??? (or whatever), the /tmp and /var/tmp
	in /etc/rc.diskless2 should NOT be nullfs mounts.  The glaring
	warning in /etc/rc.diskless1 is seemingly ignored :)

	I use the bootp/nfs-root kernel along wiht a script to do
	complete wipes of machines and then install via nfs to the
	local hard drive.

Fix: 

Replace nullfs mount for /tmp with another mfs mount point
	(should be sufficient large for isntall bins and slop).  I
	use the following in /etc/rc.diskless1

	mount_mfs -s 196608 -T qp120at dummy /tmp

	and then comment out the section involving the 
	mount_null /var/tmp /tmp
How-To-Repeat: 
	Boot with a bootp/nfs-root kernel.  mount the local disk and
	nfs mount the /usr/src & /usr/obj from buildbox, cd /usr/src
	attempt make installworld ... POOF! panic due to cp to nullfs
	mount.

Comment 1 Alexey Zelkin freebsd_committer

2000-10-22 15:38:55 UTC

Responsible Changed
From-To: freebsd-bugs->bp

One more victim for nullfs guru

Comment 2 Boris Popov freebsd_committer

2000-10-22 16:03:34 UTC

State Changed
From-To: open->analyzed

Most of the nullfs problems are fixed in -current, but not MFC'ed to -stable. 
While it is not done, mfs mount can be a better solution.

Comment 3 Boris Popov freebsd_committer

2001-06-26 05:32:17 UTC

State Changed
From-To: analyzed->closed

Most of nullfs bugs fixed in the -current and RELENG_4. 
install(1) now can be safely used on null mounts.