From owner-freebsd-current@FreeBSD.ORG Wed Apr 1 06:44:27 2009 Return-Path: Delivered-To: freebsd-current@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id 5A397106564A for ; Wed, 1 Apr 2009 06:44:27 +0000 (UTC) (envelope-from hselasky@c2i.net) Received: from swip.net (mailfe04.swip.net [212.247.154.97]) by mx1.freebsd.org (Postfix) with ESMTP id E58208FC0A for ; Wed, 1 Apr 2009 06:44:26 +0000 (UTC) (envelope-from hselasky@c2i.net) X-Cloudmark-Score: 0.000000 [] X-Cloudmark-Analysis: v=1.0 c=1 a=XvHtPtpkKJ8A:10 a=u5uu7iVke1AA:10 a=MXw7gxVQKqGXY79tIT8aFQ==:17 a=QPbusHYMeZ8bnxd80gEA:9 a=e0qvDzEypWtRVoh3FDjp6J1f8BkA:4 a=LY0hPdMaydYA:10 Received: from [62.113.132.61] (account mc467741@c2i.net HELO laptop) by mailfe04.swip.net (CommuniGate Pro SMTP 5.2.6) with ESMTPA id 1218520719; Wed, 01 Apr 2009 08:44:24 +0200 From: Hans Petter Selasky To: freebsd-current@freebsd.org Date: Wed, 1 Apr 2009 08:46:55 +0200 User-Agent: KMail/1.9.7 References: <49BD117B.2080706@163.com> <20090331100328.H46640@rust.salford.ac.uk> <20090401044011.GA51164@plebeian.afflictions.org> In-Reply-To: <20090401044011.GA51164@plebeian.afflictions.org> MIME-Version: 1.0 Content-Type: text/plain; charset="iso-8859-1" Content-Transfer-Encoding: 7bit Content-Disposition: inline Message-Id: <200904010846.55770.hselasky@c2i.net> Cc: Damian Gerow Subject: Re: ZFS checksum errors on USB attach (Was: ZFS data error without reasons) X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Discussions about the use of FreeBSD-current List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Wed, 01 Apr 2009 06:44:27 -0000 On Wednesday 01 April 2009, Damian Gerow wrote: > Mark Powell wrote: > : > the problem can be solved - The weird thing is that it will give CRC > : > errros (and permenent errors) in blocks that has not been touched (or > : > at least I think so) > : > : Can you be a little clearer? Perhaps some zpool status output with the > : steps you've taken? > > I've run into this problem four times in the past week or so. I haven't > reliably been able to reproduce it (which isn't /that/ upsetting; I don't > much like data loss, even if I can predict it), but my current hunch is > that it has something to do with uptime: the longer the system is up, the > more likely the bug is to trigger. > > Here's what happened an hour ago: > > I walked over to my laptop (Lenovo X200), and plugged in a Cowon D2 to > charge up the battery. When I tried to do other things, I received a large > number of input/output errors, so I knew I'd triggered the bug. Two things > that I tried to do: If you unload "umass" and plug a memory stick, do you see the same behaviour then? Maybe it is not directly USB related. --HPS