]> git.proxmox.com Git - mirror_zfs.git/commit
Always continue recursive destroy after error
authorAlek P <alek-p@users.noreply.github.com>
Wed, 6 Jun 2018 17:14:52 +0000 (13:14 -0400)
committerBrian Behlendorf <behlendorf1@llnl.gov>
Wed, 6 Jun 2018 17:14:52 +0000 (10:14 -0700)
commit6969afcefdfb49fb9c0fcf56240e6eb133a2c4a8
tree6f8a0b0e0e24ab47ad7434b297367e42bbaf8b64
parent62841115bc77fbd8b55d89f07cbe1cc4fb3bc520
Always continue recursive destroy after error

Currently, during a recursive zfs destroy the first error that is
encountered will stop the destruction of the datasets. Errors may
happen for a variety of reasons including competing deletions
and busy datasets.
This patch switches recursive destroy to always do a best-effort
recursive dataset destroy.

Reviewed-by: Brian Behlendorf <behlendorf1@llnl.gov>
Reviewed by: Matthew Ahrens <mahrens@delphix.com>
Signed-off-by: Alek Pinchuk <apinchuk@datto.com>
Closes #7574
cmd/zfs/zfs_main.c
tests/zfs-tests/tests/functional/cli_root/zfs_destroy/zfs_destroy_005_neg.ksh