`remove_mirror` seems to fail occasionally due to a race condition:

```
loli@openindiana:~$ sudo mkfile 512m /tmp/dsk1
loli@openindiana:~$ sudo mkfile 512m /tmp/dsk2
loli@openindiana:~$ sudo mkfile 512m /tmp/dsk3
loli@openindiana:~$ sudo zpool create -f testpool /tmp/dsk1 mirror /tmp/dsk2 
/tmp/dsk3
loli@openindiana:~$ sudo zpool remove testpool /tmp/dsk1
loli@openindiana:~$ sudo zpool remove testpool /tmp/dsk2
cannot remove /tmp/dsk2: operation not supported on this type of pool
loli@openindiana:~$ sudo zpool add testpool /tmp/dsk1 || zpool status testpool
invalid vdev specification
use '-f' to override the following errors:
/tmp/dsk1 is part of active pool 'testpool'
  pool: testpool
 state: ONLINE
  scan: none requested
remove: Evacuation of /tmp/dsk1 in progress since Sun Feb  4 09:47:45 2018
    26.5K copied out of 26.5K at 26.5K/s, 100.00% done, 0h0m to go
config:

        NAME           STATE     READ WRITE CKSUM
        testpool       ONLINE       0     0     0
          /tmp/dsk1    ONLINE       0     0     0
          mirror-1     ONLINE       0     0     0
            /tmp/dsk2  ONLINE       0     0     0
            /tmp/dsk3  ONLINE       0     0     0

errors: No known data errors
```

This is a tentative fix and isn't to be merged.
You can view, comment on, or merge this pull request online at:

  https://github.com/openzfs/openzfs/pull/534

-- Commit Summary --

  * XXX Attempt to fix remove_mirror

-- File Changes --

    M usr/src/test/zfs-tests/runfiles/delphix.run (7)
    M usr/src/test/zfs-tests/tests/functional/removal/remove_mirror.ksh (1)

-- Patch Links --

https://github.com/openzfs/openzfs/pull/534.patch
https://github.com/openzfs/openzfs/pull/534.diff

-- 
You are receiving this because you are subscribed to this thread.
Reply to this email directly or view it on GitHub:
https://github.com/openzfs/openzfs/pull/534

------------------------------------------
openzfs-developer
Archives: 
https://openzfs.topicbox.com/groups/developer/discussions/T9163fe24d217e464-M009027c5d97eef76e23d5207
Powered by Topicbox: https://topicbox.com

Reply via email to