From owner-freebsd-amd64@freebsd.org Wed Jan 6 19:12:42 2016 Return-Path: Delivered-To: freebsd-amd64@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 3D93FA654C9 for ; Wed, 6 Jan 2016 19:12:42 +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 2F1FA1BA8 for ; Wed, 6 Jan 2016 19:12:42 +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 u06JCfhM031168 for ; Wed, 6 Jan 2016 19:12:42 GMT (envelope-from bugzilla-noreply@freebsd.org) From: bugzilla-noreply@freebsd.org To: freebsd-amd64@FreeBSD.org Subject: [Bug 205974] can't detach devices from zpool Date: Wed, 06 Jan 2016 19:12:41 +0000 X-Bugzilla-Reason: CC X-Bugzilla-Type: new X-Bugzilla-Watch-Reason: None X-Bugzilla-Product: Base System X-Bugzilla-Component: kern X-Bugzilla-Version: 11.0-CURRENT X-Bugzilla-Keywords: X-Bugzilla-Severity: Affects Some People X-Bugzilla-Who: lifanov@mail.lifanov.com X-Bugzilla-Status: New X-Bugzilla-Resolution: X-Bugzilla-Priority: --- X-Bugzilla-Assigned-To: freebsd-bugs@FreeBSD.org X-Bugzilla-Flags: X-Bugzilla-Changed-Fields: bug_id short_desc product version rep_platform op_sys bug_status bug_severity priority component assigned_to reporter cc Message-ID: 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-Mailman-Approved-At: Wed, 06 Jan 2016 19:24:37 +0000 X-BeenThere: freebsd-amd64@freebsd.org X-Mailman-Version: 2.1.20 Precedence: list List-Id: Porting FreeBSD to the AMD64 platform List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Wed, 06 Jan 2016 19:12:42 -0000 https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=3D205974 Bug ID: 205974 Summary: can't detach devices from zpool Product: Base System Version: 11.0-CURRENT Hardware: amd64 OS: Any Status: New Severity: Affects Some People Priority: --- Component: kern Assignee: freebsd-bugs@FreeBSD.org Reporter: lifanov@mail.lifanov.com CC: freebsd-amd64@FreeBSD.org CC: freebsd-amd64@FreeBSD.org I migrated a zpool (mirror) from two 1T drives to two 3T drives. It had two (also mirrored) log devices. I detached both mirror devices, one at a time, and then replaced both drive= s, one at a time with autoexpand turned on. Then I re-attached the log devices in the same mirrored configuration. The pool is healthy and seems to be working normally, but I can't detach devices from it anymore. Any time I try to detach any of the four devices, = the system becomes completely unresponsive. The software version is the same. The only configuration difference is that= the new pool has 4k blocks versus 512b and also has a different pool name. After a forced reboot, pool is marked as degraded and I can plug the device back in and wait for a resilver. The device doesn't become detached. I can't produce a vmcore because the system becomes completely unresponsive= but doesn't crash. --=20 You are receiving this mail because: You are on the CC list for the bug.=