From owner-freebsd-stable@FreeBSD.ORG Fri Nov 7 21:21:50 2008 Return-Path: Delivered-To: freebsd-stable@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id 7A1A71065687 for ; Fri, 7 Nov 2008 21:21:50 +0000 (UTC) (envelope-from oberman@es.net) Received: from postal1.es.net (postal4.es.net [198.124.252.66]) by mx1.freebsd.org (Postfix) with ESMTP id 273B58FC24 for ; Fri, 7 Nov 2008 21:21:49 +0000 (UTC) (envelope-from oberman@es.net) Received: from postal1.es.net (postal3.es.net [198.128.3.207]) by postal4.es.net (Postal Node 4) with ESMTP (SSL) id NGC07949 for ; Fri, 07 Nov 2008 13:21:49 -0800 Received: from ptavv.es.net (ptavv.es.net [198.128.4.29]) by postal3.es.net (Postal Node 3) with ESMTP (SSL) id NGC85147 for ; Fri, 07 Nov 2008 13:21:47 -0800 Received: from ptavv.es.net (localhost [127.0.0.1]) by ptavv.es.net (Tachyon Server) with ESMTP id 1A47245010 for ; Fri, 7 Nov 2008 13:21:48 -0800 (PST) To: freebsd-stable@freebsd.org Mime-Version: 1.0 Content-Type: multipart/signed; boundary="==_Exmh_1226092908_20739P"; micalg=pgp-sha1; protocol="application/pgp-signature" Content-Transfer-Encoding: 7bit Date: Fri, 07 Nov 2008 13:21:48 -0800 From: "Kevin Oberman" Message-Id: <20081107212148.1A47245010@ptavv.es.net> X-Sender-IP: 198.128.3.207 X-Sender-Domain: es.net X-Recipent: ; X-Sender: X-To_Name: X-To_Domain: freebsd.org X-To: freebsd-stable@freebsd.org X-To_Email: freebsd-stable@freebsd.org X-To_Alias: freebsd-stable Subject: Problem with USB drive errors in recent 7-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: Fri, 07 Nov 2008 21:21:50 -0000 --==_Exmh_1226092908_20739P Content-Type: text/plain; charset=us-ascii Content-Disposition: inline I recently started getting errors on a fairly new USB connected SATA drive. Aside from the errors, the system was locking up as any process attempting to access the drive would lock up in disk uninterruptible wait ("D" in ps). I could not shut down the system and had to power it off. (It's a laptop.) After a reboot, I tried to fsck it and that locked up, too. I was able to recover by telling fsck to not fix the truncated inode and fix everything else. Then I ran fsck again and it was successful in fixing the inode. This happened several times. I then bought a new drive and got the identical behavior! It was not the drive. I rolled my kernel back to 9/13/08 and tried again. This time it just worked! No errors or lock up. I suspect that there are two issues. One results in the lock-up when the disk had errors and the other caused the purported disk errors. The latter has been introduced since 9/13/08. The kernel that produced the errors was from 10/21. I also ran a kernel from 10/8 which did not cause me problems, but I'm not sure that I used the USB drive with this kernel. I'll be building a 10/8 kernel later, after I have backed up some data from a failing drive (PATA, not USB, and SMART confirms that the this disk is sick). I will try to track down exactly which change triggered this ugly behavior, but that will take a number of kernel builds, so it will take a while. Has anyone else seen this? Any ideas on what changes might be the most likely cause. Could be USB, CAM, or something else, I guess. -- R. Kevin Oberman, Network Engineer Energy Sciences Network (ESnet) Ernest O. Lawrence Berkeley National Laboratory (Berkeley Lab) E-mail: oberman@es.net Phone: +1 510 486-8634 Key fingerprint:059B 2DDF 031C 9BA3 14A4 EADA 927D EBB3 987B 3751 --==_Exmh_1226092908_20739P Content-Type: application/pgp-signature -----BEGIN PGP SIGNATURE----- Version: GnuPG v2.0.9 (FreeBSD) Comment: Exmh version 2.5 06/03/2002 iD8DBQFJFLFskn3rs5h7N1ERAhb2AJ9d5gOOm0FQrUnbyYddM9rtTrSKAwCeJCOT uSAw8SHESVuzhhqZDn6FAOU= =7LVF -----END PGP SIGNATURE----- --==_Exmh_1226092908_20739P--