Date: Wed, 05 Jul 2017 01:08:33 +0000 From: bugzilla-noreply@freebsd.org To: freebsd-fs@FreeBSD.org Subject: [Bug 220472] 11.1-RC1 kernel panic (zfs recv) Message-ID: <bug-220472-3630-h63YTjaeNP@https.bugs.freebsd.org/bugzilla/> In-Reply-To: <bug-220472-3630@https.bugs.freebsd.org/bugzilla/>
index | next in thread | previous in thread | raw e-mail
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=220472 --- Comment #1 from John Kennedy <warlock@phouka.net> --- So I've done a bunch of I/O trying to narrow this down. Between 20170526 and 20170528 on a system where I thought some SSD drives were failing (recoverable checksum errors), I zfs sent | zfs recv the root disk (pool zroot) to a different disk, which I then moved to a different (current) box. Now I'm trying to move it again, and running into problems. It looks like I probably installed from installation media (11.0-RELEASE-p1 #0 r306420) and upgraded to -p10 after using beadm (possibly with some CMOS clock offset looking at the timestamps, but that should all just be relative time). I was running FreeBSD 11.0-RELEASE-p10 #0 r317487+8c96ad701987(releng/11.0) during the time that the bad snapshot I've done similar things before (and similar things after) with no problems. I can send|recv data from that filesystem up to a point (@20170526) without issues, but kernel panic after that. Right now, it seems to be isolated to the "zroot" since I can receive incrementals below that (ROOT, var, usr, etc). I'm trying to narrow it down some more. -- You are receiving this mail because: You are the assignee for the bug.home | help
Want to link to this message? Use this
URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?bug-220472-3630-h63YTjaeNP>