Return to BSD News archive
Path: sserve!newshost.anu.edu.au!munnari.oz.au!news.Hawaii.Edu!ames!agate!howland.reston.ans.net!xlink.net!fauern!cs.tu-berlin.de!klier
From: klier@cs.tu-berlin.de (Jan Klier)
Newsgroups: comp.os.386bsd.bugs
Subject: Re: FreeBSD hangs o n boot!
Date: 23 Nov 1993 09:13:13 GMT
Organization: Technical University of Berlin, Germany
Lines: 32
Message-ID: <2csk79$js8@news.cs.tu-berlin.de>
References: <matrix.753754654@noc> <2cpnl4$407@itu1.sun.ac.za> <2cq5vl$ro6@news.cs.tu-berlin.de> <CGxpBK.Bz8@unix.portal.com>
NNTP-Posting-Host: jet.cs.tu-berlin.de
Mime-Version: 1.0
Content-Type: text/plain; charset=iso-8859-1
Content-Transfer-Encoding: 8bit
chris@unix.portal.com (Chris Ding) writes:
>Jan Klier (klier@cs.tu-berlin.de) wrote:
>: A possible way to go around this problem is to edit the file /etc/rc and
>: change the line
>: fsck -p to fsck -p -l 1
>I happened to find that removing -p option from fsck in /etc/rc file
>solves the problem.
That is correct and just proves that the same thing happens on other
machines too. If you take a look at the fsck man page, or the source code
you'll see that simultanous checks are only done when the -p option is used,
because without -p the disk checks are run interactively and thus running
more than one would only confuse the user.
Taking away the -p option has the same effect than using -l 1 as I
suggested: it avoids simultanous disk checks. However I would suggest
that you use the -p option as it is speficially designed for an automatic
disk check while booting the machine.
BTW: my machine runs FreeBSD 1.0-RELEASE if that is of any interest.
And I added the timeout patch which ships around lost interrupts
in the wd driver and that didn't make it better for me yet.
jan
--
*********** Freedom is inversely proportional to security ******************
Jan Klier Berlin, Germany
e-mail: klier@cs.tu-berlin.de cis : 100022,1700
| jklier@ipk.fhg.de | 100022.1700@compuserve.com