From owner-freebsd-current  Tue Jan  6 23:50:21 1998
Return-Path: <owner-freebsd-current>
Received: (from root@localhost)
          by hub.freebsd.org (8.8.7/8.8.7) id XAA23337
          for current-outgoing; Tue, 6 Jan 1998 23:50:21 -0800 (PST)
          (envelope-from owner-freebsd-current)
Received: from alpo.whistle.com (alpo.whistle.com [207.76.204.38])
          by hub.freebsd.org (8.8.7/8.8.7) with ESMTP id XAA23321
          for <current@freebsd.org>; Tue, 6 Jan 1998 23:50:15 -0800 (PST)
          (envelope-from julian@whistle.com)
Received: (from daemon@localhost)
	by alpo.whistle.com (8.8.5/8.8.5) id XAA10145;
	Tue, 6 Jan 1998 23:46:30 -0800 (PST)
Received: from UNKNOWN(), claiming to be "current1.whistle.com"
 via SMTP by alpo.whistle.com, id smtpd010143; Tue Jan  6 23:46:23 1998
Date: Tue, 6 Jan 1998 23:43:22 -0800 (PST)
From: Julian Elischer <julian@whistle.com>
To: Simon Shapiro <shimon@simon-shapiro.org>
cc: current@freebsd.org
Subject: RE: YADR (yet another DEVFS Release)
In-Reply-To: <XFMail.980106233313.shimon@simon-shapiro.org>
Message-ID: <Pine.BSF.3.95.980106234026.2456G-100000@current1.whistle.com>
MIME-Version: 1.0
Content-Type: TEXT/PLAIN; charset=US-ASCII
Sender: owner-freebsd-current@freebsd.org
X-Loop: FreeBSD.org
Precedence: bulk

I have a slice11 in the works.
but I'm working on a strange problem with mounting floppies (it crashes).
What is the setup of slices in your machine? (dmesg output would be the 
most succinct). and which slices fail fsck?


On Tue, 6 Jan 1998, Simon Shapiro wrote:

> Howdee!
> 
> Slice10 looks real good.
> 
> The only problem I have so far, is on the new sendero;
> 
> fsck -p complains that certain partitions are busy.  This I belive to be
> incorrect.  There is nothing wrong that is detectable, but the same three
> partitions are always busy for fsck -p but will mount -a (or fsck)
> perfectly fine from the shell.
> 
> I also compiled a SLICEed SMP kernel and that looks correct too.  Managed
> to NFS mount all of Nomis on Sendero and cpio the entire machine over
> without a hitch.
> 
> Here is the configuration, in case you cared:
> 
> MB:    P6DNH2 with 2xP6-200
> RAM:   384MB
> Video: Matrox MGA 2064W graphics accelerator
> SCSI:  DPT PM3334UW w/64MB RAM
>        DPT PM3334UDW w/64MB RAM
> 
> Disks: Iomega Jaz (for testing) - Still have to play with remove-insert
>        RAID-1 for boot device - 4GB usable - Single bus
>        RAID-5 for storage - 28GB usable - Single bus shared with RAID-1
>        RAID-0 for playing around - 28GB split across 2 busses
> 
> There are two DAT drives on the system, one on each bus, as well as a
> Yamaha WORM.  They all are doing fine.
> 
> I will be adding another RAID-5 array tomorrow and hook up another CPU to
> the same pair of busses;  For multi initiator and DLM development.
> 
> I have tested the large arrays as both a single 28GB slice/partition and as
> a split/fragmented.  They both seem to be doing fine.
> 
> The only problem appears to be with fsck.  Given the standard /etc/rc
> script it fails miderably with large partitions and/or many filesystems.
> It needs the enclosed patch to work.
> 
> If fsck cannot be fixed to acomodate such a large collection of large
> disks, I'll be happy to submit a patch the /etc/rc that works.  It is a bit
> slower than the current one but works.
> 
> Thanx for the help and the functionality.
> 
> Simon
> 
> 
> 
> 
>