[Bug 219972] Unable to zpool export following some zfs recv

[bugzilla-noreply at freebsd.org]

https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=219972

            Bug ID: 219972
           Summary: Unable to zpool export following some zfs recv
           Product: Base System
           Version: 11.0-RELEASE
          Hardware: amd64
                OS: Any
            Status: New
          Severity: Affects Only Me
          Priority: ---
         Component: kern
          Assignee: freebsd-bugs at FreeBSD.org
          Reporter: pfribeiro at gmail.com

root at sunflower:~ # uname -a
FreeBSD sunflower 11.0-RELEASE-p9 FreeBSD 11.0-RELEASE-p9 #0: Tue Apr 11
08:48:40 UTC 2017    
root at amd64-builder.daemonology.net:/usr/obj/usr/src/sys/GENERIC  amd64

I must admit this is quite some odd behaviour I'm getting regarding zfs pools.

I'm trying to synchronize snapshots from another FreeBSD system (FreeNAS in
fact) to a pure FreeBSD 11-RELEASE-p9 system, with a USB 3.0-attached Seagate
8TB drive. Quite often, I'm unable to do 'zpool export master' after a 'zpool
import master'. This seems to happen more consistently after having done a 'zfs
recv'. Something alone the lines of:

root at sunflower:~ # zpool import master
root at sunflower:~ # zpool export master
root at sunflower:~ # zpool import master
root at sunflower:~ # zpool export master
root at sunflower:~ # zpool import master
root at sunflower:~ # zpool export master
cannot export 'master': pool is busy
root at sunflower:~ # zpool export master
cannot export 'master': pool is busy

I note that there are no processes using the pool. I have also tried using
'zpool import -N master', but the result is often the same. I have also tried
'zpool export -f master' but to no avail.

I don't see any erroneous messages in dmesg, neither in /var/log/messages. I
initially was using geli with an AES encrypted device being used to create the
zfs pool, but I have since then tested without crypto, and the problem
persists.

Following this behaviour I am then unable to export the pool till I reboot the
system.

I have opened a GitHub issue with the original guide I followed at:
https://github.com/hughobrien/zfs-remote-mirror/issues/7, and subsequently
posted on the FreeBSD forum: https://forums.freebsd.org/threads/61291/. But
quite frankly, I am almost giving up on this storage idea, because I cannot get
to the bottom of this issue. There are no obvious logged errors that I can poke
at. I would appreciate some guidance to confirm this erroneous behaviour
further.

I see that there are some vaguely related bugs like #201735, but in my case I
am not accessing any particular folder or file at all.

Thanks

-- 
You are receiving this mail because:
You are the assignee for the bug.