On Tue, Aug 28, 2007 at 04:27:22PM +0200, Pascal Hofstee wrote: > Hi, > > For the last couple of weeks now I've occasionally been getting kernel > panics through ZFS (usually during heavy disk-i/o on the ZFS volume) > usually at the time this happened i was busy in X and therefore unable > to get to the console and force a kernel-dump. Today though it seems i > was lucky and actually managed to catch a kernel panic while in console > mode. Below is the actual panic message, i tried looking at the actual > backtrace but all the interesting frames are purely addresses without > any symbol information. I'll assume this is because of zfs and friends > being loaded as KLDs. Any information on how to provide a proper > backtrace including all symbols involved would be appreciated. > > uname -a: > FreeBSD trinity.zion 7.0-CURRENT FreeBSD 7.0-CURRENT #29: Sun Aug 26 > 20:19:12 CEST 2007 pascal_at_trinity.zion:/usr/obj/usr/src/sys/TRINITY > i386 > > panic: ZFS: I/O failure (write on <unknown> off 0: zio 0xc66a9cf0 [L0 > ZFS plain file] 20000L/20000P DVA[0]=<0:a126e0000:20000> fletcher2 > uncompressed LE contiguous birth=7004722 fill=1 > cksum=2dc0c354bd8ccc27:85745b74c1352a7f:72188a8646f7f624:28d89f21264ed4f2): e^ When you don't use redundant configuration (no mirror, no raidz, no copies>1) then ZFS is going to panic on a write failure. It looks like ZFS found a bad block on your disk. -- Pawel Jakub Dawidek http://www.wheel.pl pjd_at_FreeBSD.org http://www.FreeBSD.org FreeBSD committer Am I Evil? Yes, I Am!
This archive was generated by hypermail 2.4.0 : Wed May 19 2021 - 11:39:16 UTC