From owner-freebsd-stable Fri May 22 16:22:39 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id QAA12479 for freebsd-stable-outgoing; Fri, 22 May 1998 16:22:39 -0700 (PDT) (envelope-from owner-freebsd-stable@FreeBSD.ORG) Received: from sendero.simon-shapiro.org (sendero.simon-shapiro.org.142.69.207.in-addr.arpa [207.69.142.25] (may be forged)) by hub.freebsd.org (8.8.8/8.8.8) with SMTP id QAA12430 for ; Fri, 22 May 1998 16:22:25 -0700 (PDT) (envelope-from shimon@sendero.simon-shapiro.org) Received: (qmail 4153 invoked by uid 1000); 23 May 1998 00:23:33 -0000 Message-ID: X-Mailer: XFMail 1.3 [p0] on FreeBSD X-Priority: 3 (Normal) Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 8bit MIME-Version: 1.0 In-Reply-To: <199805221824.LAA01141@dingo.cdrom.com> Date: Fri, 22 May 1998 20:23:33 -0400 (EDT) Reply-To: shimon@simon-shapiro.org Organization: The Simon Shapiro Foundation From: Simon Shapiro To: Mike Smith Subject: Re: DPT install problem Cc: freebsd-scsi@FreeBSD.ORG, freebsd-stable@FreeBSD.ORG, Tom Sender: owner-freebsd-stable@FreeBSD.ORG Precedence: bulk On 22-May-98 Mike Smith wrote: >> >> >> Currently it is pretty hard to bootstrap a new DPT system. You have >> to >> be able to build a kernel somewhere else as sysinstall will install a >> non-DPT kernel, and you can't use sysinstall to allocate large DPT >> partitions. I fear for the new user. > > New users are less than likely to be presented with such a situation. > > However, there are a couple of things that you personally (and other > concerned users) can do to help the situation. > > - Contribute commentary (as you have), documentation and source/ > procedural fixes. Remeber that FreeBSD is a volunteer project - > your support means that it will continue to improve. > - Donate a DPT controller to our testing pool so that we can test > with it. Chances are we can scrape enough disks together in one > place to meet the 20GB mark if we have one. I recently donated TWO DPT controllers and FIVE disk drives. They went to two separate FreeBSD prominent figures, but still do not add up to 20GB. I will add this sort of test to my regression testing. But, as I said, I mostly test on 3.0-current and do not see this problem there. An ajacent problem, is that fsck will fail on such filesystems. The failure mode is fsck -p in /etc/rc. It does not have, by default enough resources to run a large parallel fsck. I added the following to /etc/rc: swapon -a if [ $1x = autobootx ]; then echo Automatic reboot in progress... + ulimit -t unlimited + ulimit -f unlimited + ulimit -d unlimited + ulimit -s unlimited + ulimit -c unlimited + ulimit -m unlimited + ulimit -l unlimited fsck -p This (or its equivalent) may remove the problem from sysinstall. Simon --- Sincerely Yours, Simon Shapiro Shimon@Simon-Shapiro.ORG 770.265.7340 To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-stable" in the body of the message