Alek P 6969afcefd 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

2018-06-06 10:14:52 -07:00

..

callbacks

Multi-modifier protection (MMP)

2017-07-13 13:54:00 -04:00

cmd

Fix calloc(3) arguments order

2018-04-12 10:50:39 -07:00

include

Add pool state /proc entry, "SUSPENDED" pools

2018-06-06 09:33:54 -07:00

tests

Always continue recursive destroy after error

2018-06-06 10:14:52 -07:00

Makefile.am

OpenZFS 7503 - zfs-test should tail ::zfs_dbgmsg on test failure

2017-04-12 13:36:48 -07:00