[Bug 216881] zpool detach hangs if autoexpand is set to on.
bugzilla-noreply at freebsd.org
bugzilla-noreply at freebsd.org
Tue Feb 7 12:26:45 UTC 2017
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=216881
Bug ID: 216881
Summary: zpool detach hangs if autoexpand is set to on.
Product: Base System
Version: 11.0-RELEASE
Hardware: amd64
OS: Any
Status: New
Severity: Affects Some People
Priority: ---
Component: kern
Assignee: freebsd-bugs at FreeBSD.org
Reporter: jmc-freebsd2 at milibyte.co.uk
CC: freebsd-amd64 at FreeBSD.org
CC: freebsd-amd64 at FreeBSD.org
FreeBSD curlew.lan 11.0-RELEASE-p2 FreeBSD 11.0-RELEASE-p2 #0: Mon Oct 24
06:55:27 UTC 2016
root at amd64-builder.daemonology.net:/usr/obj/usr/src/sys/GENERIC amd64
zpool detach hangs and eventually freezes the entire system if autoexpand is
set to on.
After rebooting the detached device is still shown in the pool but is
inaccessible and cannot be removed
For example, starting with this pool:
root at fbsd11:~ # zpool status
pool: test
state: ONLINE
scan: resilvered 74.5K in 0h0m with 0 errors on Mon Feb 6 13:55:04
2017
config:
NAME STATE READ WRITE CKSUM
test ONLINE 0 0 0
mirror-0 ONLINE 0 0 0
gpt/ztest1 ONLINE 0 0 0
gpt/ztest2 ONLINE 0 0 0
errors: No known data errors
root at fbsd11:~ # zpool get autoexpand
NAME PROPERTY VALUE SOURCE
test autoexpand on local
If I attempt to detach test gpt/ztest2 it hangs and after rebooting I have the
following:
root at fbsd11:~ # zpool status
pool: test
state: DEGRADED
status: One or more devices could not be opened. Sufficient replicas
exist for
the pool to continue functioning in a degraded state.
action: Attach the missing device and online it using 'zpool online'.
see: http://illumos.org/msg/ZFS-8000-2Q
scan: resilvered 74.5K in 0h0m with 0 errors on Mon Feb 6 13:55:04
2017
config:
NAME STATE READ WRITE CKSUM
test DEGRADED 0 0 0
mirror-0 DEGRADED 0 0 0
gpt/ztest1 ONLINE 0 0 0
12467057712079289495 UNAVAIL 0 0 0 was
/dev/gpt/ztest2
errors: No known data errors
At this stage the former gpt/ztest2 cannot be detached or reattached until I
set autoexpand to off which then enables me to detach it.
A similar problem was resolved with FreeNAS in November and might be relevant -
https://bugs.pcbsd.org/issues/14337
--
You are receiving this mail because:
You are on the CC list for the bug.
More information about the freebsd-amd64
mailing list