*BSD News Article 25748


Return to BSD News archive

Xref: sserve comp.os.386bsd.bugs:2002 comp.os.386bsd.questions:7796
Path: sserve!newshost.anu.edu.au!munnari.oz.au!metro!ultima!kralizec.zeta.org.au!godzilla.zeta.org.au!not-for-mail
From: bde@kralizec.zeta.org.au (Bruce Evans)
Newsgroups: comp.os.386bsd.bugs,comp.os.386bsd.questions
Subject: Re: FreeBSD 1.0.2 with NFS-mounted /usr - strange fsck problem
Date: 8 Jan 1994 12:44:24 +1100
Organization: Kralizec Dialup Unix Sydney - +61-2-837-1183, v.32bis and v.42bis
Lines: 14
Message-ID: <2gl35oINNgf@godzilla.zeta.org.au>
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: godzilla.zeta.org.au

In article <2g6mhh$ibo@fw.novatel.ca>, Herb Peyerl <hpeyerl@sidney> 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.

It is fixed in the wx driver.
-- 
Bruce Evans  bde@kralizec.zeta.org.au