Richard L. Hamilton wrote: >> On May 14, 2009, at 5:48 PM, Edward Pilatowicz wrote: >> >>> this is great. >>> >>> i just have one question. is there anyway to undo >> a "zfs destroy -d" >>> request? (it seems to me that if zfs destroy -d >> was implmented in >>> terms >>> of a snapshot property, say autodelete=on|off, this >> would be easy.) >> >> Ed, >> >> Just like with "zfs destroy", there's no way to >> undo a "zfs destroy >> -d". >> The snapshot might be destroyed immediately if >> there's no reason to >> defer the operation, and we have no way to undo that. > > Obviously one can't undo it if it does happen immediately. But if > the destroy is deferred, it might be desirable to be able to cancel it. > Perhaps that's what the OP meant. Given the description of being marked > for deletion when the conditions are met, in principle one might think it > possible to clear that flag.
> Which raises another question: what happens if someone does > a zfs destroy -d, it is deferred, and they then try to salvage the situation > with zfs hold? Will the hold take effect (preventing the destroy until it is > released), > or will the hold fail? I would hope so and that is what I was going to suggest I'd do to "undo" the deferred destroy. -- Darren J Moffat
