From owner-freebsd-questions Mon Sep 18 11:36:48 2000 Delivered-To: freebsd-questions@freebsd.org Received: from leizaola.com (leizaola.com [202.66.66.6]) by hub.freebsd.org (Postfix) with ESMTP id B00CA37B423 for ; Mon, 18 Sep 2000 11:36:44 -0700 (PDT) Received: from p22.tnt.hk.net (p22.tnt.hk.net [202.66.202.22]) by leizaola.com (8.9.3/8.9.0) with ESMTP id CAA10935 for ; Tue, 19 Sep 2000 02:36:30 +0800 Date: Tue, 19 Sep 2000 02:38:10 +0800 (Taipei Standard Time) From: "Maren S. Leizaola" To: freebsd-questions@FreeBSD.ORG Subject: Large Partitions corrupting when getting full. Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-questions@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Calling All Disk Gurus, I have ASUS P3V4x board based machine with an Intel Ether Express board. I find that when /dev/wd0s1d gets full it will corrupt itself. When installing FreeBSD 3.3 it complained about the disk geometry, but managed to get it to install. The FS config is: Filesystem 1K-blocks Used Avail Capacity Mounted on /dev/wd0s1a 198399 19985 162543 11% / /dev/wd0s1f 1016303 25580 909419 3% /home /dev/wd0s1d 13606585 27819 12490240 0% /other /dev/wd0s1g 1016303 75640 859359 8% /tmp /dev/wd0s1e 644919 486280 107046 82% /usr /dev/wd0s1h 14887224 1443484 12252763 11% /var procfs 4 4 0 100% /proc --- Version: FreeBSD www 3.3-RELEASE FreeBSD 3.3-RELEASE #0: Thu Sep 16 23:40:35 GMT 1999 jkh@highwing.cdrom.com:/usr/src/sys/compile/GENERIC i386 --- Drive : IBM UltraDMA wdc0: unit 0 (wd0): wd0: 32634MB (66835440 sectors), 66305 cyls, 16 heads, 63 S/T, 512 B/S I've tried not using an UDMA66 cable and still the same. I've tried changing to Seaget drives of same size, and get the same errors and also same corruption. --- I also get one of these errors every 3-4 days: Jun 26 23:41:41 www /kernel: wd0: interrupt timeout (status 58 error 0) Jun 26 23:41:41 www /kernel: wd0: wdtimeout() DMA status 4 I've tried different drives, different boards, etc... still the same problem. I've reinstalled several times and stil no luck. ---- Is this an issue with FreeBSD 3.3 not being able to handle these bigger drives? Regards, Maren. PS. CC me on replies as I am not subscribed to the list. To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-questions" in the body of the message