freebsd stable - Jan 2015 - 8.4-p23 zfs panic

Howdy,

I have a box that had been running 8.4-p1 for about a year and a half with no
issues.  Pretty standard 2U Supermicro box, ZFS-based setup with a few jails. 
Mainly used to store backups and other utility tasks.  Most backups happen with
rsync, but two vmware boxes nfs mount this host and dump snapshots to it.  It
also runs poudriere builds when that time rolls around.

Two days ago I updated to 8.4-p23.  I ran a few large poudriere builds the night
before last, and then queued a few more last night.  Overnight the box paniced
(and in the annoying way where it does not automatically reboot nor generate a
dump).

Any known issues that I?ve missed?  What sorts of zfs changes have gone on
between p1 and p23?

Wish I had more info, but without a dump, I don?t know what else I can share.  I
think it?s safe to assume a poudriere build was in-progress, finishing, or
starting when the panic occurred.

Image of monitor as remote hands found it here:

http://i.imgur.com/hwOVFyu.jpg

OCR of same:

FreeBSD/amd64 (trunk.bway.net) (ttyv0) 
login: panic: solaris assert: dsl_prop_unregister(ds, "xattr",
xattr_changed_cb, zfsvfs) == 0, file:
/usr/src/sys/modules/zfs/../../cddl/contrib/opensolaris/uts/common/fs/zfs/zfs_vfsops.c,
line: 1218
cpuid = 1 
Uptime: 2d18h38041s 
Cannot dump. Device not defined or unavailable. 
Automatic reboot in 15 seconds - press a key on the console to abort
--> Press a key on the console to reboot, 
--> or switch off the system now. 

Thanks,

Charles

-- 
Charles Sprickman
NetEng/SysAdmin
Bway.net - New York's Best Internet www.bway.net
spork at bway.net - 212.655.9344

-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA512

On 01/30/15 15:22, Charles Sprickman wrote:
> Howdy,
> 
> I have a box that had been running 8.4-p1 for about a year and a
> half with no issues.  Pretty standard 2U Supermicro box, ZFS-based
> setup with a few jails.  Mainly used to store backups and other
> utility tasks.  Most backups happen with rsync, but two vmware
> boxes nfs mount this host and dump snapshots to it.  It also runs
> poudriere builds when that time rolls around.
> 
> Two days ago I updated to 8.4-p23.  I ran a few large poudriere
> builds the night before last, and then queued a few more last
> night.  Overnight the box paniced (and in the annoying way where it
> does not automatically reboot nor generate a dump).
> 
> Any known issues that I?ve missed?  What sorts of zfs changes have
> gone on between p1 and p23?
There is one ZFS change between p1 and p23 but I am pretty sure it
shouldn't have anything to do with this panic.
> Wish I had more info, but without a dump, I don?t know what else I
> can share.  I think it?s safe to assume a poudriere build was
> in-progress, finishing, or starting when the panic occurred.
> 
> Image of monitor as remote hands found it here:
> 
> http://i.imgur.com/hwOVFyu.jpg
> 
> OCR of same:
> 
> FreeBSD/amd64 (trunk.bway.net) (ttyv0) login: panic: solaris
> assert: dsl_prop_unregister(ds, "xattr", xattr_changed_cb,
zfsvfs)
> == 0, file:
>
/usr/src/sys/modules/zfs/../../cddl/contrib/opensolaris/uts/common/fs/zfs/zfs_vfsops.c,
> line: 1218 cpuid = 1 Uptime: 2d18h38041s
I think this is fixed by r248653 (will@; cc'ed), which was merged to
stable/9 but never to stable/8.

Cheers,
- -- 
Xin LI <delphij at delphij.net>    https://www.delphij.net/
FreeBSD - The Power to Serve!           Live free or die
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v2.1.1 (FreeBSD)

iQIcBAEBCgAGBQJUzBjYAAoJEJW2GBstM+ns0m4P/ROGUAFj62bMgUjQY71WIgsz
5RlCvSZcdYf2YWdwl3w4BFuQ9ZJGA356A6VHGX2sCUH/lt5H746/1OCClfw36Wal
x88D2Y1Orha4xhSuJmtfaDD0X6Yj3vLwkY3Wp3tAbzwat8RPCXbwugd7pgjKtVmV
wNQ8x4i9udg1Y/ND98DRb1f/AYJQ8/imiqCBfd65hRCpFIYI1v/GWKMl4FNl+8X2
E76plXASLE1zYCUo7DL0y1RzHSpHC4Vgvd6zm2zUDxb7RslaD2PFlgb6Qg49BrTW
kO0FyQfiXXGrkQNbwyI5c0YhQZ5f2ney5yyrkYa0ZIRFJ2jb4Y66YXWhvVYAqB4K
NRWEwVKAbZdFxFolnrc+rqCNAJmB/yprGvCZkIzNvvaouqKLJgJQOJgmd8boZ201
JS/HUA+IsrNDa3V3rK/uEnZgDE4cN8bqLiwRs2U7HqC9eqxY7lxNIr1L8N9+9uou
nQI9JiR0/b4WnE9/q67Twlv4c9a8w90AOUNmKHUstoONQl0MsKVHrsG/q6UbhxrG
kpY8q+G+bDBmZbkvfyusAJJ0KUEJHKFjjry9B3J1VtKzkk51s2tkCs6ddign79Rs
CnHvp6RzWA2qgeB4fh95uUOW062886kLe1q3NJVbn17vEFoXu9kA4eVmDDEq6w7w
dkU1CNIdKtB5OiJxI+uV
=N49B
-----END PGP SIGNATURE-----