Date: Tue, 21 Nov 2017 19:30:46 +0000 From: Shiva Bhanujan <Shiva.Bhanujan@Quorum.com> To: "cem@freebsd.org" <cem@freebsd.org> Cc: Andriy Gapon <avg@freebsd.org>, "freebsd-fs@freebsd.org" <freebsd-fs@freebsd.org>, Shiva Bhanujan <Shiva.Bhanujan@Quorum.com> Subject: RE: zio_done panic in 10.3 Message-ID: <3A5A10BE32AC9E45B4A22F89FC90EC0701C367D636@QLEXC01.Quorum.local> In-Reply-To: <CAG6CVpVT=4iid4xi0yw3AJe4kbBNEGj6zVCKfozq_-8CgGYfag@mail.gmail.com> References: <3A5A10BE32AC9E45B4A22F89FC90EC0701C367D3D1@QLEXC01.Quorum.local> <5021a016-9193-b626-78cf-54ffa3929e22@FreeBSD.org> <3A5A10BE32AC9E45B4A22F89FC90EC0701C367D562@QLEXC01.Quorum.local>, <CAG6CVpVT=4iid4xi0yw3AJe4kbBNEGj6zVCKfozq_-8CgGYfag@mail.gmail.com>
next in thread | previous in thread | raw e-mail | index | archive | help
it did get compressed to 0.5G - still too big to send via email. I did = send some more debug information by running kgdb on the core file to = Andriy, and I'm waiting for any analysis that he might provide. From: Conrad Meyer =5Bcem=40freebsd.org=5D Sent: Tuesday, November 21, 2017 9:04 AM To: Shiva Bhanujan Cc: Andriy Gapon; freebsd-fs=40freebsd.org Subject: Re: zio_done panic in 10.3 Have you tried compressing it with e.g. xz or zstd? On Tue, Nov 21, 2017 at 5:19 AM, Shiva Bhanujan <Shiva.Bhanujan=40quorum.com> wrote: > the vmcore file is =7E4G. can you please tell me how to deliver this to = you? > > > > From: Andriy Gapon =5Bavg=40FreeBSD.org=5D > Sent: Tuesday, November 21, 2017 1:49 AM > To: Shiva Bhanujan;=20 freebsd-fs=40freebsd.org > Subject: Re: zio_done panic in 10.3 > > > On 20/11/2017 22:34, Shiva Bhanujan wrote: >> Hello, >> >> I'm getting a kernel panic in FreeBSD 10.3 p22 (r324806M). >> >> KDB: stack backtrace: >> =230 0xffffffff80982fe0 at kdb_backtrace+0x60 >> =231 0xffffffff80945cb6 at vpanic+0x126 >> =232 0xffffffff80945b83 at panic+0x43 >> =233 0xffffffff80d4ac6b at trap_fatal+0x36b >> =234 0xffffffff80d4af6d at trap_pfault+0x2ed >> =235 0xffffffff80d4a5ea at trap+0x47a >> =236 0xffffffff80d305b2 at calltrap+0x8 >> =237 0xffffffff8094db5d at _sx_xlock+0x5d >> =238 0xffffffff81a4ccec at zio_done+0x92c >> =239 0xffffffff81a486ea at zio_execute+0x10a >> =2310 0xffffffff80993e15 at taskqueue_run_locked+0xe5 >> =2311 0xffffffff809948a8 at taskqueue_thread_loop+0xa8 >> =2312 0xffffffff8090f13a at fork_exit+0x9a >> =2313 0xffffffff80d30aee at fork_trampoline+0xe >> >> We are doing send/receive of zfs snapshots by piping it through mbuffer = and netcat. I can't seem to relate send/receive to the above backtrace. >> >> The closest bug that I've found w/ a panic close to the above is as = follows: >> >>=20 https://bugs.freebsd.org/bugzilla/show_bug.cgi?format=3Dmultiple&id=3D181966 >> >> I haven't been able to find any commits against this backtrace. Can = anybody please point me to anything that might have addressed this issue? = please let me know if there is any additional information that you might = need. > > Do you have a crash dump (vmcore) ? > If not, could you please get one? > > -- > Andriy Gapon > > > _______________________________________________ >=20 freebsd-fs=40freebsd.org mailing list >=20 https://lists.freebsd.org/mailman/listinfo/freebsd-fs > To unsubscribe, send any mail to = =22freebsd-fs-unsubscribe=40freebsd.org=22
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?3A5A10BE32AC9E45B4A22F89FC90EC0701C367D636>