<div dir="ltr">Here's the dump from the panic:<div><br></div><div><a href="ftp://ftp.nrg.wustl.edu/pub/zfs/mirpool03-xattr-20180830-vmdump.1">ftp://ftp.nrg.wustl.edu/pub/zfs/mirpool03-xattr-20180830-vmdump.1</a><br></div><div><br></div><div><br></div></div><div class="gmail_extra"><br><div class="gmail_quote">On Thu, Aug 30, 2018 at 9:29 AM, Schweiss, Chip <span dir="ltr"><<a href="mailto:chip@innovates.com" target="_blank">chip@innovates.com</a>></span> wrote:<br><blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex"><div dir="ltr">I've seen this panic twice now in the past couple weeks. Does anyone know if there is a patch already that fixes this? Looks like another xattr problem.<div><br></div><div><div># fmdump -Vp -u b7c9840b-8bb1-cbbc-e165-a5b6fa<wbr>34078b</div><div>TIME UUID SUNW-MSG-ID</div><div>Aug 30 2018 08:29:32.089419000 b7c9840b-8bb1-cbbc-e165-a5b6fa<wbr>34078b SUNOS-8000-KL</div><div><br></div><div> TIME CLASS ENA</div><div> Aug 30 08:27:50.8299 ireport.os.sunos.panic.dump_pe<wbr>nding_on_device 0x0000000000000000</div><div><br></div><div>nvlist version: 0</div><div> version = 0x0</div><div> class = list.suspect</div><div> uuid = b7c9840b-8bb1-cbbc-e165-a5b6fa<wbr>34078b</div><div> code = SUNOS-8000-KL</div><div> diag-time = 1535635766 223254</div><div> de = fmd:///module/software-diagnos<wbr>is</div><div> fault-list-sz = 0x1</div><div> fault-list = (array of embedded nvlists)</div><div> (start fault-list[0])</div><div> nvlist version: 0</div><div> version = 0x0</div><div> class = defect.sunos.kernel.panic</div><div> certainty = 0x64</div><div> asru = sw:///:path=/var/crash//.b7c98<wbr>40b-8bb1-cbbc-e165-a5b6fa34078<wbr>b</div><div> resource = sw:///:path=/var/crash//.b7c98<wbr>40b-8bb1-cbbc-e165-a5b6fa34078<wbr>b</div><div> savecore-succcess = 0</div><div> os-instance-uuid = b7c9840b-8bb1-cbbc-e165-a5b6fa<wbr>34078b</div><div> panicstr = BAD TRAP: type=d (#gp General protection) rp=ffffd001e9855360 addr=ffffd063784ee8d0</div><div> panicstack = unix:real_mode_stop_cpu_stage2<wbr>_end+b203 () | unix:trap+a70 () | unix:cmntrap+e6 () | zfs:zfs_getattr+1a0 () | genunix:fop_getattr+a8 () | genunix:xattr_dir_getattr+16c () | genunix:fop_getattr+a8 () | nfssrv:rfs4_delegated_getattr+<wbr>20 () | nfssrv:acl3_getxattrdir+102 () | nfssrv:common_dispatch+5ab () | nfssrv:acl_dispatch+2d () | rpcmod:svc_getreq+1c1 () | rpcmod:svc_run+e0 () | rpcmod:svc_do_run+8e () | nfs:nfssys+111 () | unix:brand_sys_sysenter+1d3 () |</div><div> crashtime = 1535633923</div><div> panic-time = Thu Aug 30 07:58:43 2018 CDT</div><div> (end fault-list[0])</div><div><br></div><div> fault-status = 0x1</div><div> severity = Major</div><div> __ttl = 0x1</div><div> __tod = 0x5b87f13c 0x5546cf8</div></div><div><br></div><div>Let me know what other information I can provide here.</div><span class="HOEnZb"><font color="#888888"><div><br></div><div>-Chip</div><div><br></div></font></span></div>
</blockquote></div><br></div>