Skip site navigation (1)Skip section navigation (2)
Date:      Sat, 19 Sep 1998 09:42:12 -0400 (EDT)
From:      Snob Art Genre <benedict@echonyc.com>
To:        current@FreeBSD.ORG
Subject:   Re: more fs fear
Message-ID:  <Pine.GSO.4.02.9809190935490.15363-100000@echonyc.com>

next in thread | raw e-mail | index | archive | help
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 <face color=red>, I unmounted the fs and fscked it again, and now
it seems to be fine</face>.

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: <CONNER CFP2107S  2.14GB 5767> 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: <QUANTUM FIREBALL_TM3200S 300X> 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



Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?Pine.GSO.4.02.9809190935490.15363-100000>