From owner-freebsd-stable@FreeBSD.ORG Sat Nov 19 18:04:37 2005 Return-Path: X-Original-To: freebsd-stable@freebsd.org Delivered-To: freebsd-stable@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 96B2916A41F for ; Sat, 19 Nov 2005 18:04:37 +0000 (GMT) (envelope-from sean-freebsd@farley.org) Received: from mail.farley.org (farley.org [67.64.95.201]) by mx1.FreeBSD.org (Postfix) with ESMTP id EEFAE43D45 for ; Sat, 19 Nov 2005 18:04:36 +0000 (GMT) (envelope-from sean-freebsd@farley.org) Received: from thor.farley.org (thor.farley.org [IPv6:2001:470:1f01:290:1::5]) by mail.farley.org (8.13.1/8.13.1) with ESMTP id jAJI4YXQ008573 for ; Sat, 19 Nov 2005 12:04:34 -0600 (CST) (envelope-from sean-freebsd@farley.org) Date: Sat, 19 Nov 2005 12:06:00 -0600 (CST) From: =?ISO-8859-1?Q?Se=E1n_C=2E_Farley?= To: freebsd-stable@freebsd.org Message-ID: <20051119112837.O15168@thor.farley.org> MIME-Version: 1.0 Content-Type: MULTIPART/MIXED; BOUNDARY="0-1580538870-1132422079=:15168" Content-ID: <20051119115351.K901@thor.farley.org> Subject: File system corruption with ATA RAID-1 on 6-STABLE X-BeenThere: freebsd-stable@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Production branch of FreeBSD source code List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Sat, 19 Nov 2005 18:04:37 -0000 This message is in MIME format. The first part should be readable text, while the remaining parts are likely unreadable without MIME-aware tools. --0-1580538870-1132422079=:15168 Content-Type: TEXT/PLAIN; CHARSET=ISO-8859-1; format=flowed Content-Transfer-Encoding: QUOTED-PRINTABLE Content-ID: <20051119115351.B901@thor.farley.org> I installed 6.0 on a system with two SATA drives in RAID-1. 5.4 is installed on a standard IDE channel. All appeared to work well until sometime after updating the system to 6-STABLE, installing the Nvidia driver and copying a lot of data (mainly ogg files) from my old hard drive onto it. I started seeing a multitude of READ_DMA (or maybe WRITE_DMA) errors in /var/log/messages. The system was beginning to slow down a lot, so I rebooted. Since then I have been unable to keep it up without a panic after an fsck in single-user mode. I realize this does not tell much, but just when ld.so.hints is being removed due to being corrupt the follow panic appears: Panic: ffs_valloc: dup alloc The panic may just be from a system that is too corrupted. I am amazed it still boots. I am not sure if it is -STABLE or -RELEASE where the problem really started since I did not copy anything over until everything look good. I did not lose anything important, so I do not need to save anything. How should I proceed or does anyone know if this is a known problem? I am able to mount the partitions within the 5.4 system without issue. Possible related PR's: i386/75531 (http://www.freebsd.org/cgi/query-pr.cgi?pr=3Di386/75531) kern/89069 (http://www.freebsd.org/cgi/query-pr.cgi?pr=3Dkern/89069) Other oddities: 1. /var/log/messages showed some messages from my 5.4 system at first. Are those stored in the BIOS? 2. While copying the data over, I noticed the system running slower and slower. This may have been from all the messages being saved into messages about READ_DMA. Configuration: ASUS A7V880 atapci0: port 0xeff0-0xeff7,0xefe4-0xefe7,0xefa8-0xefaf,0xefe0-0xefe3,0xef90-0xef9f, 0xe800-0xe8ff irq 20 at device 15.0 on pci0 ad4: 152627MB at ata2-master SATA150 ad6: 152627MB at ata3-master SATA150 ar0: 152627MB status: READY ar0: disk0 READY (master) using ad4 at ata2-master ar0: disk1 READY (mirror) using ad6 at ata3-master Se=E1n --=20 sean-freebsd@farley.org --0-1580538870-1132422079=:15168--