From owner-freebsd-current Sat Sep 19 06:42:43 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id GAA05939 for freebsd-current-outgoing; Sat, 19 Sep 1998 06:42:43 -0700 (PDT) (envelope-from owner-freebsd-current@FreeBSD.ORG) Received: from echonyc.com (echonyc.com [198.67.15.2]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id GAA05934 for ; Sat, 19 Sep 1998 06:42:41 -0700 (PDT) (envelope-from benedict@echonyc.com) Received: from localhost by echonyc.com (8.9.1/8.9.1) with SMTP id JAA28529 for ; Sat, 19 Sep 1998 09:42:12 -0400 (EDT) Date: Sat, 19 Sep 1998 09:42:12 -0400 (EDT) From: Snob Art Genre Reply-To: ben@rosengart.com To: current@FreeBSD.ORG Subject: Re: more fs fear Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On Sat, 19 Sep 1998, Eivind Eklund wrote: > I'd suggest a followup detailing setup, including whether you run > soft updates, whether you run with Luoqi's last patch, whether you > run CAM, which controller and disks you've got if you do, when your > -current is from, and how old the relevant filesystem is. Also how > large the write that failed was - was it attempting to write a so > large file that the removal of that single file could create the > amount of free space? Well , I unmounted the fs and fscked it again, and now it seems to be fine. I don't know why this fsck caught the problem while the fsck at boot didn't. Just for completeness' sake: no soft updates at this time, no Luoqi's last patch (it's only relevant to soft-updates panics, no?), yes CAM, Buslogic BT-948 with the following disks: da0 at bt0 bus 0 target 0 lun 0 da0: Fixed Direct Access SCSI2 device da0: 3.300MB/s transfers, Tagged Queueing Enabled da0: 2048MB (4194304 512 byte sectors: 255H 63S/T 261C) da1 at bt0 bus 0 target 6 lun 0 da1: Fixed Direct Access SCSI2 device da1: 3.300MB/s transfers, Tagged Queueing Enabled da1: 3067MB (6281856 512 byte sectors: 255H 63S/T 391C) I don't remember the age of the filesystem, because I don't remember whether I newfs'd it when soft updates ate sd1 a couple of months ago. BTW, it was a very small write on a <1MB file that tickled this problem (I'm not sure which file, but it happened when I started rc5des). I can use ktrace to get the name and hence the exact size of the file, if necessary. Ben "You have your mind on computers, it seems." To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message