From owner-freebsd-usb@FreeBSD.ORG Sun May 29 15:14:59 2011 Return-Path: Delivered-To: freebsd-usb@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id 23D64106564A for ; Sun, 29 May 2011 15:14:59 +0000 (UTC) (envelope-from utisoft@gmail.com) Received: from mail-bw0-f54.google.com (mail-bw0-f54.google.com [209.85.214.54]) by mx1.freebsd.org (Postfix) with ESMTP id A7F8E8FC0C for ; Sun, 29 May 2011 15:14:57 +0000 (UTC) Received: by bwz12 with SMTP id 12so3456710bwz.13 for ; Sun, 29 May 2011 08:14:56 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=gamma; h=domainkey-signature:mime-version:reply-to:from:date:message-id :subject:to:content-type; bh=zYFTqdzC7JauI1ijh8Fhuau2db9W0OOY0hkavE3qkT8=; b=VFw0I2Wr/7/S3qo+vTbfmytNWvgskEg08zjAqnqcfbXjk7g0IsTpYL4dAhugN6yqCT Fg7eArEktUGzZuVuMN02J4h1rBf69tNbv8QEWxLa4ojdSQW2sckgQEnpQqU6237hlCES 9ntx6MQLSDPcgPECDR/jPcNG8p8I0o2+TdtlQ= DomainKey-Signature: a=rsa-sha1; c=nofws; d=gmail.com; s=gamma; h=mime-version:reply-to:from:date:message-id:subject:to:content-type; b=CoHwAZi9KmG/TCyRAjxxRPTFd377/hWTueV9wUNgSS/s43hUXxm5psdaJ0GwHURAZf 0Sn9JVJmTv84llZGRWdVGtiDXX2XNvh1qEFZ7lg7AF4KHADkX+JMA7Pf1xGwNczi/s5N k/vjyC1iWC0/1cd/UTz/uuSf2qPpTKS06nauo= Received: by 10.204.57.135 with SMTP id c7mr3400568bkh.88.1306680778448; Sun, 29 May 2011 07:52:58 -0700 (PDT) MIME-Version: 1.0 Received: by 10.204.66.81 with HTTP; Sun, 29 May 2011 07:52:28 -0700 (PDT) From: Chris Rees Date: Sun, 29 May 2011 15:52:28 +0100 Message-ID: To: freebsd-usb@freebsd.org Content-Type: text/plain; charset=ISO-8859-1 Subject: USB hard drive g_vfs_done() error=5 X-BeenThere: freebsd-usb@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list Reply-To: utisoft@gmail.com List-Id: FreeBSD support for USB List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Sun, 29 May 2011 15:14:59 -0000 Hi all, I'm afraid I've also got the infamous error 5 problem on my Macbook. USB hard drive seems to work fine as it's newfs'd a couple of times, but after a little while (using USB hard drive as backup destination with rsync) it gives me these: [crees@zeus]~% dmesg |tail g_vfs_done():da0s1[WRITE(offset=41748480, length=2048)]error = 5 g_vfs_done():da0s1[WRITE(offset=41750528, length=2048)]error = 5 g_vfs_done():da0s1[WRITE(offset=41752576, length=2048)]error = 5 g_vfs_done():da0s1[WRITE(offset=41754624, length=2048)]error = 5 g_vfs_done():da0s1[WRITE(offset=41756672, length=2048)]error = 5 g_vfs_done():da0s1[WRITE(offset=41758720, length=2048)]error = 5 g_vfs_done():da0s1[WRITE(offset=41760768, length=2048)]error = 5 g_vfs_done():da0s1[WRITE(offset=41762816, length=12288)]error = 5 g_vfs_done():da0s1[WRITE(offset=41775104, length=2048)]error = 5 g_vfs_done():da0s1[WRITE(offset=41777152, length=2048)]error = 5 Unfortunately I can't seem to stop it doing this, and every time I've just unplugged the drive in the past the system panics... I'd really rather avoid that since it's my main server. [crees@zeus]~% uname -a FreeBSD zeus.bayofrum.net 8.2-RELEASE-p1 FreeBSD 8.2-RELEASE-p1 #0: Sat Apr 30 15:09:06 BST 2011 root@zeus.bayofrum.net:/usr/obj/usr/src/sys/ZEUS i386 Kernel config file is at [1]. I've tried the patch from [2], and this stops the AutoSense failed messages I used to get, but not these. Perhaps oddly related, when these messages start tab-completion in tcsh sometimes hangs -- even for unrelated directories such as % ls /roo^VTAB causes a hang. Any ideas/patches/information I've missed? The drive works perfectly in 'Windows', and I also tried it on my Ubuntu netbook. Chris [1] http://www.bayofrum.net/~crees/ZEUS (diff to GENERIC at http://www.bayofrum.net/~crees/ZEUS.diff) [2] http://www.freebsd.org/cgi/query-pr.cgi?pr=usb/150401