*BSD News Article 25646


Return to BSD News archive

Path: sserve!newshost.anu.edu.au!munnari.oz.au!news.Hawaii.Edu!ames!haven.umd.edu!darwin.sura.net!udel!news.sprintlink.net!clark.net!clark.net!not-for-mail
From: ack@clark.net (Eric S. Hvozda)
Newsgroups: comp.os.386bsd.bugs
Subject: Re: [NetBSD 0.9] patch to wd.c for IDE controller weirdnesses
Date: 6 Jan 1994 09:29:39 -0500
Organization: Clark Internet Services, Inc.
Lines: 15
Message-ID: <2gh78j$nmd@explorer.clark.net>
References: <2ga4l7$i75@explorer.clark.net> <2gea0a$18q@explorer.clark.net> <2geifb$a6d@darum.uni-mannheim.de> <2gg0fu$9bk@uuneo.neosoft.com>
NNTP-Posting-Host: explorer.clark.net
Mime-Version: 1.0
Content-Type: text/plain; charset=US-ASCII
Content-Transfer-Encoding: 7bit

In article <2gg0fu$9bk@uuneo.neosoft.com>,
Peter da Silva <peter@news.NeoSoft.com> wrote:
>What is this 'you shouldn't check partitions on two WD drives at the
>same time?  I've been running Bonkers for months under 386BSD like
>that (two Maxtor XT4380E and an Ultrastor 12F). Is this a NetBSD problem
>or an IDE problem? It sure didn't hit my ESDI drives.

I had the lockup problem with fscking two IDE's until I added -l1 to fsck
in /etc/rc, then the problem went away.  Otherwise you have to make almost
all the scan orders in /etc/fstab 1 to make fsck do the right thing.  It seems
to be a problem with fscking IDE drives in tandem.  I had it with NetBSD, but
I dunno if the other kids in the *BSD family have the same problem...
-- 
Ack!
Creek, not creek; Pop not soda; Car needs washed...