*BSD News Article 86640


Return to BSD News archive

Path: euryale.cc.adfa.oz.au!newshost.carno.net.au!harbinger.cc.monash.edu.au!munnari.OZ.AU!spool.mu.edu!howland.erols.net!nntp.crl.com!news3.crl.com!nexp.crl.com!usenet
From: "Jordan K. Hubbard" <jkh@FreeBSD.org>
Newsgroups: comp.unix.bsd.freebsd.misc
Subject: Re: Optimum ccd
Date: Fri, 17 Jan 1997 01:23:42 -0800
Organization: Walnut Creek CDROM
Lines: 15
Message-ID: <32DF451E.794BDF32@FreeBSD.org>
References: <5bitfe$ckf@news.ziplink.net>
NNTP-Posting-Host: time.cdrom.com
Mime-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Content-Transfer-Encoding: 7bit
X-Mailer: Mozilla 3.01 (X11; I; FreeBSD 3.0-CURRENT i386)
To: mi@ALDAN.ziplink.net..remove-after-`net'
Xref: euryale.cc.adfa.oz.au comp.unix.bsd.freebsd.misc:33940

Mikhail Teterin wrote:
> Another thing. If there is a need to fsck the /dev/rccd0c, fsck
> will hang the system :( I found that using c-partitions of my drives
> for ccd is _wrong_, but do not know exactly how to change the
> situtation:  ccd0    192     none    /dev/sd2s1c /dev/sd3s1c
> /dev/sd4s1c /dev/sd6s1c

I don't think this is actually a ccd-related problem, however.  I have
fsck hang on a normal, non-ccd filesystem on one of my boxes here - a
bug in the Adaptec sequencer code causing the driver to hang under
certain circumstances.  Justin is aware of the problem and has been
working on a solution.
-- 
- Jordan Hubbard
  President, FreeBSD Project