Date: Wed, 06 Jan 2016 19:12:41 +0000 From: bugzilla-noreply@freebsd.org To: freebsd-amd64@FreeBSD.org Subject: [Bug 205974] can't detach devices from zpool Message-ID: <bug-205974-6@https.bugs.freebsd.org/bugzilla/>
next in thread | raw e-mail | index | archive | help
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.=
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?bug-205974-6>