- Code: Select all
sh-3.2$ sudo zpool import -o readonly=on fourgig
sh-3.2$ sudo zpool destroy fourgig
sh-3.2$ sudo zpool import
pool: fourgig
id: 5691477073133955531
state: ONLINE
action: The pool can be imported using its name or numeric identifier.
config:
fourgig ONLINE
GPTE_4E4E357C-C7ED-4FD4-9B6D-F2358B9C2E03 ONLINE
sh-3.2$ sudo zpool import fourgig
sh-3.2$ sudo zpool destroy fourgig
sh-3.2$ sudo zpool import
no pools available to import
sh-3.2$ sudo kextstat | grep greenbytes
109 1 0xffffff7f807a6000 0x19b000 0x19b000 com.getgreenbytes.filesystem.zfs (2012.09.23) <13 7 5 4 3 1>
110 0 0xffffff7f80943000 0x6000 0x6000 com.getgreenbytes.driver.zfs (2012.09.14) <109 13 7 5 4 3 1>
sh-3.2$
Issue
The pool to which the zpool destroy subcommand applied was subsequently imported. In other words:
- supposedly destroyed, but not destroyed.
Background
The test above was performed after reading MacZFS prototype issue 51, destroying a read-only pool fails. A highlight:
>> … stick with the Illumos behaviour …
– that is, successful destruction.