Return to BSD News archive
Path: euryale.cc.adfa.oz.au!newshost.carno.net.au!harbinger.cc.monash.edu.au!lucy.swin.edu.au!news.rmit.EDU.AU!news.unimelb.edu.au!munnari.OZ.AU!news.Hawaii.Edu!news.caldera.com!enews.sgi.com!nntprelay.mathworks.com!news.mathworks.com!news-peer.sprintlink.net!news.sprintlink.net!Sprint!feed1.news.erols.com!newsfeed.internetmci.com!news.wwa.com!news.ucdavis.edu!trefoil.bogs.org!greg From: greg@trefoil.bogs.org (Greg Shenaut) Newsgroups: comp.unix.bsd.freebsd.misc Subject: install 2.2.1 (mfs?) file system full Date: 6 Jun 1997 19:52:06 GMT Organization: BOGS Research Group Lines: 38 Message-ID: <5n9pp6$227$1@mark.ucdavis.edu> Reply-To: gkshenaut@ucdavis.edu NNTP-Posting-Host: bogslab.ucdavis.edu X-Newsreader: TIN [version 1.2 PL2] Xref: euryale.cc.adfa.oz.au comp.unix.bsd.freebsd.misc:42540 I've been trying to install version 2.2.1 from a CDROM via FTP on an old 386SX machine with 8MB RAM, a 125MB IDE drive, an MGA, and an NE2000 clone. The IDE interface also has two serial ports, a parallel port, and a game port. Invariably, and almost immediately (far before it touches the hard disk), I get a /: write failed, files system full error message. I also get bus errors sometimes. While this sounds like flaky hardware, I installed BSD/OS 3.0 on exactly the same hardware (except I had to change the ne2000's io address), using the remote CD installation, with no errors, plus the system has now been up about a day (cumulatively) with no errors. But when I take down this apparently perfectly-running BSD/OS system, change the jumper on the network card, and try to build an fbsd2.2.1 system, I never succeed--it always bombs out, in the same way. I did get the newer/boot.flp from www.freebsd.org, but it didn't change anything I could see (I started out with the one off the CD). I also ran the fixit disk, and it stayed up long enough for me to df the mfs; it was far from empty, although every time I tried a command like "ls bin", I got the above error, plus a bus error most of the time. I'd appreciate a suggestion (later today or tomorrow I'll try a different motherboard, but it's hard for me to understand how it could perform perfectly under BSD/OS and fail so utterly under FBSD). Actually one idea that occurred to me is that the memory load maps might be different enough that the MFS may land in higher RAM under FBSD, RAM which tends not to get used on the unloaded BSD/OS system--in other words, there could be a memory problem in one bank of upper RAM. -Greg