When doing "zfs create -V" and "zfs rename" operations on the same zpool in parallel, there is a high chance for a deadlock leading to a complete hang of the zpool in question (i.e., all further zfs operations hang indefinitely).
Attached you find a simple perl script that should trigger the bug (the pool variable needs to be set to your pool name), if run in two shells at the same time:
$ for i in `seq 1 100`; do sudo ./zfsrenamebug.pl "A$i"; done
$ for i in `seq 1 100`; do sudo ./zfsrenamebug.pl "B$i"; done
When doing "zfs create -V" and "zfs rename" operations on the same zpool in parallel, there is a high chance for a deadlock leading to a complete hang of the zpool in question (i.e., all further zfs operations hang indefinitely).
Attached you find a simple perl script that should trigger the bug (the pool variable needs to be set to your pool name), if run in two shells at the same time:
$ for i in `seq 1 100`; do sudo ./zfsrenamebug.pl "A$i"; done
$ for i in `seq 1 100`; do sudo ./zfsrenamebug.pl "B$i"; done
Reported upstream in https:/ /github. com/zfsonlinux/ zfs/issues/ 4404 and apparently fixed with the linked commits.