Date: Thu, 20 Sep 2018 15:31:03 +0000 From: bugzilla-noreply@freebsd.org To: bugs@FreeBSD.org Subject: [Bug 231516] [ZFS] Crash upon dectection of failed drive. Message-ID: <bug-231516-227-uC6DAJnbw9@https.bugs.freebsd.org/bugzilla/> In-Reply-To: <bug-231516-227@https.bugs.freebsd.org/bugzilla/> References: <bug-231516-227@https.bugs.freebsd.org/bugzilla/>
next in thread | previous in thread | raw e-mail | index | archive | help
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=3D231516 --- Comment #2 from Sean Bruno <sbruno@FreeBSD.org> --- da3 is the disk that is failing. Starting up the jails and indexing files = on the zftp pool will cause the panic in this ticket. I *can* remove the driv= e, but I want to wait for some diagnostics from ZFS folks first. root@ftp-mirror0.isc:~ # zpool status pool: zftp state: ONLINE scan: scrub repaired 150K in 0 days 02:03:31 with 0 errors on Fri Aug 17 05:19:19 2018 config: NAME STATE READ WRITE CKSUM zftp ONLINE 0 0 0 raidz1-0 ONLINE 0 0 0 da0p1 ONLINE 0 0 0 da1p1 ONLINE 0 0 0 da2p1 ONLINE 0 0 0 da3p1 ONLINE 0 0 0 da4p1 ONLINE 0 0 0 da5p1 ONLINE 0 0 0 da6p1 ONLINE 0 0 0 da7p1 ONLINE 0 0 0 errors: No known data errors pool: zroot state: ONLINE scan: scrub repaired 0 in 0 days 03:16:08 with 0 errors on Fri Aug 17 06:31:58 2018 config: NAME STATE READ WRITE CKSUM zroot ONLINE 0 0 0 mirror-0 ONLINE 0 0 0 ada0p3 ONLINE 0 0 0 ada1p3 ONLINE 0 0 0 errors: No known data errors --=20 You are receiving this mail because: You are the assignee for the bug.=
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?bug-231516-227-uC6DAJnbw9>