As Bob Bishop wrote ... > I'm getting the 'blocks of NULLs in NFS-mounted files' problem repeatably > with last night's -current (cvsup'd at Wed Apr 14 04:02:34 BST 1999) > running both on server and client (except that the client's kernel is 24hrs > older than that). > > It happens during a kernel build on the client, so both the sources and > objects are being accessed via NFS. During the 'generating linker set > emulation glue for ELF' phase, a lot of the .o's turn up with blocks of > NULLs. The rest of the world builds fine, but /usr/obj is local so there is > little or no NFS writing going on in that case.
I have the impression I'm seeing similar things here. I have a 3.1 NFS server holding the -current sources. I build kernels over NFS using a -current testbox. Sometimes it builds kernels alright, sometimes you get kernels that panic with 100% repeatability. Just doing a config -r and a rebuild normally fixes this. The same thing happened when the NFS server was still at 2.2.8-stable Buildworlds with a local /usr/obj seem to work just fine. Groeten / Cheers, Wilko _ ______________________________________________________________________ | / o / / _ Arnhem, The Netherlands |/|/ / / /( (_) Bulte WWW : http://www.tcja.nl _______________________ Powered by FreeBSD ___ http://www.freebsd.org _____ To Unsubscribe: send mail to majord...@freebsd.org with "unsubscribe freebsd-current" in the body of the message
