From owner-freebsd-current Sat Feb 10 22:02:31 1996 Return-Path: owner-current Received: (from root@localhost) by freefall.freebsd.org (8.7.3/8.7.3) id WAA14852 for current-outgoing; Sat, 10 Feb 1996 22:02:31 -0800 (PST) Received: from hauki.clinet.fi (root@hauki.clinet.fi [194.100.0.1]) by freefall.freebsd.org (8.7.3/8.7.3) with ESMTP id WAA14847 for ; Sat, 10 Feb 1996 22:02:27 -0800 (PST) Received: from newzetor.clinet.fi (root@newzetor.clinet.fi [194.100.0.11]) by hauki.clinet.fi (8.7.3/8.6.4) with ESMTP id IAA15444; Sun, 11 Feb 1996 08:02:20 +0200 (EET) Received: (hsu@localhost) by newzetor.clinet.fi (8.7.3/8.6.4) id IAA02168; Sun, 11 Feb 1996 08:02:20 +0200 (EET) Date: Sun, 11 Feb 1996 08:02:20 +0200 (EET) Message-Id: <199602110602.IAA02168@newzetor.clinet.fi> From: Heikki Suonsivu To: Warner Losh Cc: freebsd-current@freebsd.org In-reply-to: Warner Losh's message of 10 Feb 1996 07:45:28 +0200 Subject: Re: How Organization: Clinet Ltd, Espoo, Finland References: <199602100543.WAA25958@rover.village.org> Sender: owner-current@freebsd.org Precedence: bulk In article <199602100543.WAA25958@rover.village.org> Warner Losh writes: : For anything other than initial install, copying, archiving, async : is a bad bet. For those particular operations, it's a big win. It can also be good on a partition devoted solely to news that is allowed to be newfs on data corruption as well... With current full-feed news flow and innd, there will soon be no option other than battery-backed-up scsi controller or async mounts. I have survived with async mounts for news disks since last summer, and the damn thing crashes often enough that I can say you can make it without serious data loss, as long as you run fsck -y for news disks on boot :-) -- Heikki Suonsivu, T{ysikuu 10 C 83/02210 Espoo/FINLAND, hsu@clinet.fi mobile +358-40-5519679 work +358-0-4375360 fax -4555276 home -8031121