Date: Thu, 28 May 2009 15:42:52 +0200 From: Kurt Jaeger <lists@c0mplx.org> To: freebsd-stable@freebsd.org Subject: zdb core (same problem?) Message-ID: <20090528134252.GB10978@home.opsec.eu> In-Reply-To: <3c1674c90905280052q281f6172j2409fe2d64db6914@mail.gmail.com> References: <3c1674c90905201643m540c8b1v8a8bd88f071c233d@mail.gmail.com> <4A1D0F2B.4030006@restart.be> <ed91d4a80905271104g2a824d0fna004d1c4f3126c67@mail.gmail.com> <3c1674c90905280052q281f6172j2409fe2d64db6914@mail.gmail.com>
next in thread | previous in thread | raw e-mail | index | archive | help
Hi! > Adding to rw_init looks fine, but I'd rather find out why owner isn't > NULL when the calling convention expects it. Getting a backtrace from > where the assert is hit would be helpful. I have another zdb mypool crash on a 7.2-STABLE. f7# zpool history mypool History for 'mypool': 2009-05-24.21:58:36 zpool create -m /spare1 mypool ad4s3d 2009-05-24.22:11:35 zfs set compression=on mypool 2009-05-25.08:07:04 zpool upgrade -a 2009-05-27.22:31:21 zpool scrub mypool 2009-05-27.22:31:26 zpool scrub mypool For a gdb with backtrace see http://opsec.eu/backup/zdb-backtrace -- pi@opsec.eu +49 171 3101372 11 years to go !
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?20090528134252.GB10978>