zpool destroy whilst readonly=on

This forum is to find answers to problems you may be having with ZEVO Community Edition.

Moderators: jhartley, MSR734, nola

zpool destroy whilst readonly=on

Post by grahamperrin » Sat Sep 07, 2013 9:50 am

An extract from http://pastebin.com/3bQ7tvPk

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.
grahamperrin Offline

User avatar
 
Posts: 1596
Joined: Fri Sep 14, 2012 10:21 pm
Location: Brighton and Hove, United Kingdom

Return to Troubleshooting

Who is online

Users browsing this forum: bileyqrkq, ilovezfs, toduefiwu and 0 guests

cron