Date: Tue, 13 Jun 2017 23:56:07 +0000 From: bugzilla-noreply@freebsd.org To: freebsd-bugs@FreeBSD.org Subject: [Bug 219972] Unable to zpool export following some zfs recv Message-ID: <bug-219972-8@https.bugs.freebsd.org/bugzilla/>
next in thread | raw e-mail | index | archive | help
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=3D219972 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@FreeBSD.org Reporter: pfribeiro@gmail.com root@sunflower:~ # uname -a FreeBSD sunflower 11.0-RELEASE-p9 FreeBSD 11.0-RELEASE-p9 #0: Tue Apr 11 08:48:40 UTC 2017=20=20=20=20 root@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 poo= ls. 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 Seaga= te 8TB drive. Quite often, I'm unable to do 'zpool export master' after a 'zpo= ol import master'. This seems to happen more consistently after having done a = 'zfs recv'. Something alone the lines of: root@sunflower:~ # zpool import master root@sunflower:~ # zpool export master root@sunflower:~ # zpool import master root@sunflower:~ # zpool export master root@sunflower:~ # zpool import master root@sunflower:~ # zpool export master cannot export 'master': pool is busy root@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 tri= ed '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 --=20 You are receiving this mail because: You are the assignee for the bug.=
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?bug-219972-8>