Date: Mon, 25 Sep 2000 13:21:33 -0400 (EDT) From: "Sean O'Connell" <sto@stat.Duke.EDU> To: FreeBSD-gnats-submit@freebsd.org Subject: conf/21540: installworld panics for diskless clients Message-ID: <200009251721.e8PHLXI51003@feta.isds.duke.edu>
next in thread | raw e-mail | index | archive | help
>Number: 21540 >Category: conf >Synopsis: installworld panics for diskless clients >Confidential: no >Severity: serious >Priority: medium >Responsible: freebsd-bugs >State: open >Quarter: >Keywords: >Date-Required: >Class: sw-bug >Submitter-Id: current-users >Arrival-Date: Mon Sep 25 10:30:01 PDT 2000 >Closed-Date: >Last-Modified: >Originator: Sean O'Connell >Release: FreeBSD 4.1-STABLE i386 >Organization: Institute of Statistics and Decision Sciences >Environment: FreeBSD 4.1-STABLE (-current as well, I would imagine) >Description: 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. >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. >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 >Release-Note: >Audit-Trail: >Unformatted: To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-bugs" in the body of the message
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?200009251721.e8PHLXI51003>