Date: Thu, 04 Feb 2016 00:39:19 +0000 From: bugzilla-noreply@freebsd.org To: freebsd-fs@FreeBSD.org Subject: [Bug 206109] zpool import of corrupt pool causes system to reboot Message-ID: <bug-206109-3630-RQyinMrsxs@https.bugs.freebsd.org/bugzilla/> In-Reply-To: <bug-206109-3630@https.bugs.freebsd.org/bugzilla/> References: <bug-206109-3630@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=3D206109 jha3@zips.uakron.edu changed: What |Removed |Added ---------------------------------------------------------------------------- CC| |jha3@zips.uakron.edu --- Comment #1 from jha3@zips.uakron.edu --- I have experienced the same issue here (except for the faulty RAM part). I = have a 6 x 3 TB WD zpool, running on an M1015 SAS raid card, with 16 GB ECC RAM. While watching a movie on the array late last week, the system crashed, entering a reboot loop. Note, the OS is installed on separate flash drive. fsck indicated no errors= on the OS drive. Note also that I have a second zpool of 6 drives which can st= ill be mounted/ imported without issue. I upgraded from freeBSD 10.0 to 10.2 at the end of Dec 2015. As in the OP's case, the array can still be mounted read-only. Memtest was run for 48 hours and indicated no RAM errors. SMART reports indicate no evidence of drive failure. I am surprised and dismayed that an error in a zpool array can cause this t= ype of behavior in the system. I would have expected an umount or some similar indication; not a system crash or reboot loop. --=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-206109-3630-RQyinMrsxs>