Summary: | [zfs] boot fail from zfs root while the pool resilvering | ||
---|---|---|---|
Product: | Base System | Reporter: | Alexei Volkov <Alexei.Volkov> |
Component: | kern | Assignee: | freebsd-bugs (Nobody) <bugs> |
Status: | Open --- | ||
Severity: | Affects Only Me | ||
Priority: | Normal | ||
Version: | 8.0-RELEASE | ||
Hardware: | Any | ||
OS: | Any |
Description
Alexei Volkov
2009-11-26 07:20:01 UTC
Responsible Changed From-To: freebsd-bugs->freebsd-fs Over to maintainer(s). I found, that it keep fail booting if has at least one device not ONLINE and pool state DEGRADED. For instance [root@livecd8:/]# zpool status pool: tank0 state: DEGRADED scrub: none requested config: NAME STATE READ WRITE CKSUM tank0 DEGRADED 0 0 0 raidz1 DEGRADED 0 0 0 replacing DEGRADED 0 0 0 12996219703647995136 UNAVAIL 0 298 0 was /dev/gpt/QM00002 gpt/SN023432 ONLINE 0 0 0 gpt/SN091234 ONLINE 0 0 0 errors: No known data errors considered as degraded even it has replace gpt/QM00002 with new gpt/SN023432. Detaching UNAVAIL component turns pool to ONLINE state back. [root@livecd8:/]# zpool detach tank0 12996219703647995136 [root@livecd8:/]# zpool status pool: tank0 state: ONLINE scrub: none requested config: NAME STATE READ WRITE CKSUM tank0 ONLINE 0 0 0 raidz1 ONLINE 0 0 0 gpt/SN023432 ONLINE 0 0 0 gpt/SN091234 ONLINE 0 0 0 errors: No known data errors This case lets to boot from tank0. It also keeps booting fine in case of component is manually turns to OFFLINE state in any combination, for instance like [root@fresh-inst:~]# zpool status pool: tank0 state: DEGRADED status: One or more devices has experienced an unrecoverable error. An attempt was made to correct the error. Applications are unaffected. action: Determine if the device needs to be replaced, and clear the errors using 'zpool clear' or replace the device with 'zpool replace'. see: http://www.sun.com/msg/ZFS-8000-9P scrub: none requested config: NAME STATE READ WRITE CKSUM tank0 DEGRADED 0 0 0 raidz1 DEGRADED 0 0 0 gpt/SN023432 ONLINE 0 0 0 gpt/SN091234 OFFLINE 0 921 0 errors: No known data errors For bugs matching the following criteria: Status: In Progress Changed: (is less than) 2014-06-01 Reset to default assignee and clear in-progress tags. Mail being skipped |