From owner-freebsd-fs@freebsd.org Thu Feb 4 00:39:20 2016 Return-Path: Delivered-To: freebsd-fs@mailman.ysv.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:1900:2254:206a::19:1]) by mailman.ysv.freebsd.org (Postfix) with ESMTP id C75D1A9B62D for ; Thu, 4 Feb 2016 00:39:20 +0000 (UTC) (envelope-from bugzilla-noreply@freebsd.org) Received: from kenobi.freebsd.org (kenobi.freebsd.org [IPv6:2001:1900:2254:206a::16:76]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (Client did not present a certificate) by mx1.freebsd.org (Postfix) with ESMTPS id B8357B3A for ; Thu, 4 Feb 2016 00:39:20 +0000 (UTC) (envelope-from bugzilla-noreply@freebsd.org) Received: from bugs.freebsd.org ([127.0.1.118]) by kenobi.freebsd.org (8.15.2/8.15.2) with ESMTP id u140dIxD089645 for ; Thu, 4 Feb 2016 00:39:20 GMT (envelope-from bugzilla-noreply@freebsd.org) From: bugzilla-noreply@freebsd.org To: freebsd-fs@FreeBSD.org Subject: [Bug 206109] zpool import of corrupt pool causes system to reboot Date: Thu, 04 Feb 2016 00:39:19 +0000 X-Bugzilla-Reason: AssignedTo X-Bugzilla-Type: changed X-Bugzilla-Watch-Reason: None X-Bugzilla-Product: Base System X-Bugzilla-Component: kern X-Bugzilla-Version: 10.2-RELEASE X-Bugzilla-Keywords: X-Bugzilla-Severity: Affects Only Me X-Bugzilla-Who: jha3@zips.uakron.edu X-Bugzilla-Status: New X-Bugzilla-Resolution: X-Bugzilla-Priority: --- X-Bugzilla-Assigned-To: freebsd-fs@FreeBSD.org X-Bugzilla-Flags: X-Bugzilla-Changed-Fields: cc Message-ID: In-Reply-To: References: Content-Type: text/plain; charset="UTF-8" Content-Transfer-Encoding: quoted-printable X-Bugzilla-URL: https://bugs.freebsd.org/bugzilla/ Auto-Submitted: auto-generated MIME-Version: 1.0 X-BeenThere: freebsd-fs@freebsd.org X-Mailman-Version: 2.1.20 Precedence: list List-Id: Filesystems List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Thu, 04 Feb 2016 00:39:20 -0000 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.=