From owner-freebsd-stable Sun Sep 6 17:00:35 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id RAA13526 for freebsd-stable-outgoing; Sun, 6 Sep 1998 17:00:35 -0700 (PDT) (envelope-from owner-freebsd-stable@FreeBSD.ORG) Received: from pericles.IPAustralia.gov.au (pericles.IPAustralia.gov.au [202.14.186.30]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id RAA13517 for ; Sun, 6 Sep 1998 17:00:31 -0700 (PDT) (envelope-from Carl.Makin@ipaustralia.gov.au) From: Carl.Makin@ipaustralia.gov.au Received: (from smap@localhost) by pericles.IPAustralia.gov.au (8.8.7/8.8.7) id KAA03415 for ; Mon, 7 Sep 1998 10:00:19 +1000 (EST) (envelope-from Carl.Makin@ipaustralia.gov.au) X-Authentication-Warning: pericles.IPAustralia.gov.au: smap set sender to using -f Received: from noteshub01.aipo.gov.au(192.3.1.21) by pericles.IPAustralia.gov.au via smap (V2.0) id xma003397; Mon, 7 Sep 98 09:59:52 +1000 Received: by noteshub01.aipo.gov.au(Lotus SMTP MTA v4.6.1 (569.2 2-6-1998)) id 4A256678.00001259 ; Mon, 7 Sep 1998 10:00:46 +1000 X-Lotus-FromDomain: IP_AUSTRALIA To: freebsd-stable@FreeBSD.ORG Message-ID: <4A256677.00831072.00@noteshub01.aipo.gov.au> Date: Mon, 7 Sep 1998 09:58:45 +1000 Subject: fsck problem with ccd partitions Mime-Version: 1.0 Content-type: text/plain; charset=us-ascii Content-Disposition: inline Sender: owner-freebsd-stable@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Hi, I've got 2 9gb Barracudas striped using ccd on a 2.2.7-STABLE (built from last Friday's sources). When booting it stops with; cannot alloc 8309762 bytes for lncntp /dev/rccd0c: CAN'T CHECK FILE SYSTEM. /dev/rccd0c: UNEXPECTED INCONSISTENCY; RUN fsck MANUALLY. I then "fsck /dev/rccd0c", which works fine, do a "mount -a" and exit the shell so the system keeps booting. Immediately after I hit "d" I get; "ccdconfig: open: /dev/ccd0c: Device Busy" and the boot then runs and ends fine... Does anyone have any ideas on why this is happening? Thanks, Carl. To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-stable" in the body of the message