Return to BSD News archive
Xref: sserve comp.os.386bsd.bugs:1962 comp.os.386bsd.questions:7687
Path: sserve!newshost.anu.edu.au!munnari.oz.au!spool.mu.edu!news.sol.net!news.sol.net!not-for-mail
From: jgreco@solaria.sol.net (Joe Greco)
Newsgroups: comp.os.386bsd.bugs,comp.os.386bsd.questions
Subject: Re: FreeBSD 1.0.2 with NFS-mounted /usr - strange fsck problem
Date: 3 Jan 1994 00:08:39 -0600
Organization: Solaria Public Access UNIX - Milwaukee, WI
Lines: 23
Message-ID: <2g8cp7$ard@solaria.mil.wi.us>
References: <2g0ptu$j72@solaria.mil.wi.us> <2g1rii$ln8@wzv.win.tue.nl> <2g5q8d$kub@fleis.moneng.mei.com> <2g6mhh$ibo@fw.novatel.ca>
NNTP-Posting-Host: solaria.mil.wi.us
In comp.os.386bsd.bugs article <2g6mhh$ibo@fw.novatel.ca>, hpeyerl@sidney (Herb Peyerl) wrote:
:Joe Greco (jgreco@fleis.moneng.mei.com) wrote:
:: some other playing. Changing the fsck -p to a plain fsck works, but has
:: obvious disadvantages on a system that should run unattended. It seems like
:: it is hanging when it forks off the fsck for wd0e.
:
:The is the exact description of one of the original race conditions in the
:wd driver. To my knowledge; this bug has never been fixed in any of the
:wd/wx drivers for all controllers... Note; I said "to my knowledge" so I
:could be wrong.
But this does not explain the fact that on this same system with the same
hardware setup, it has worked flawlessly with the entire FreeBSD
distribution loaded locally. I {c,sh}ould try this again, since we did swap
a drive (identical), but it seems like a higher level software problem.
It even worked doing parallel fscks, although it was slow as all hell..
... Joe
-------------------------------------------------------------------------------
Joe Greco - Systems Administrator jgreco@ns.sol.net
Solaria Public Access UNIX - Milwaukee, WI 414/342-4847