From owner-freebsd-current Sat Sep 19 12:28:15 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id MAA11043 for freebsd-current-outgoing; Sat, 19 Sep 1998 12:28:15 -0700 (PDT) (envelope-from owner-freebsd-current@FreeBSD.ORG) Received: from Gatekeeper.Alameda.net (gatekeeper.Alameda.net [207.90.181.2]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id MAA11038 for ; Sat, 19 Sep 1998 12:28:13 -0700 (PDT) (envelope-from ulf@Gatekeeper.Alameda.net) Received: by Gatekeeper.Alameda.net (8.8.8/8.8.6) id MAA03971; Sat, 19 Sep 1998 12:27:50 -0700 (PDT) Message-ID: <19980919122750.B1516@Alameda.net> Date: Sat, 19 Sep 1998 12:27:50 -0700 From: Ulf Zimmermann To: ben@rosengart.com, current@FreeBSD.ORG Subject: Re: more fs fear Reply-To: ulf@Alameda.net References: Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii X-Mailer: Mutt 0.91.1i In-Reply-To: ; from Snob Art Genre on Sat, Sep 19, 1998 at 09:42:12AM -0400 Organization: Alameda Networks, Inc. X-Operating-System: FreeBSD 2.2.6-STABLE Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On Sat, Sep 19, 1998 at 09:42:12AM -0400, Snob Art Genre wrote: > 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. So, the fsck at boot time failed and the fsck at run time failed not ? Sounds like the problem I ran into with /etc/login.conf. > > 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 -- Regards, Ulf. --------------------------------------------------------------------- Ulf Zimmermann, 1525 Pacific Ave., Alameda, CA-94501, #: 510-769-2936 Alameda Networks, Inc. | http://www.Alameda.net | Fax#: 510-521-5073 To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message