Date: Tue, 15 Apr 2014 17:39:25 +1200 From: Phil Murray <pmurray@nevada.net.nz> To: Andriy Gapon <avg@FreeBSD.org> Cc: freebsd-fs@freebsd.org, stable@FreeBSD.org Subject: Re: Panic in ZFS, solaris assert: sa.sa_magic == 0x2F505A Message-ID: <E44610BC-B49E-4320-B2A9-FAC1A6854FBE@nevada.net.nz> In-Reply-To: <5347C5A0.3030806@FreeBSD.org> References: <A746AB69-2EB9-47C6-958D-965DF5DF8AA6@nevada.net.nz> <5347C5A0.3030806@FreeBSD.org>
next in thread | previous in thread | raw e-mail | index | archive | help
On 11/04/2014, at 10:36 pm, Andriy Gapon <avg@FreeBSD.org> wrote: > on 11/04/2014 11:02 Phil Murray said the following: >> Hi there, >>=20 >> I=92ve recently experienced two kernel panics on 8.4-RELEASE (within = 2 days of each other, and both around the same time of day oddly) with = ZFS. Sorry no dump available, but panic below. >>=20 >> Any ideas where to start solving this? Will upgrading to 9 (or 10) = solve it? >=20 > By chance, could the system be running zfs recv at the times when the = panics > happened? I think it might be related to this bug reported on ZFS-on-linux when = upgrading from v3 -> v5, which is exactly what I=92ve done on this = machine: https://github.com/zfsonlinux/zfs/issues/2025 In my case, the bogus sa.sa_magic value looks like this: panic:solaris asset: sa.sa_magic =3D=3D 0x2F505A (0x5112fb3d =3D=3D = 0x2f505a), file:=20 $ date -r 0x5112fb3d Thu Feb 7 13:54:21 NZDT 2013 Cheers Phil
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?E44610BC-B49E-4320-B2A9-FAC1A6854FBE>