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. --HPSReceived on Wed Apr 01 2009 - 04:44:27 UTC
This archive was generated by hypermail 2.4.0 : Wed May 19 2021 - 11:39:45 UTC