[Bug 235132] bectl destroy … cannot destroy …: dataset already exists

[bugzilla-noreply at freebsd.org]

https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=235132

Rob <rob.fx907 at gmail.com> changed:

           What    |Removed                     |Added
----------------------------------------------------------------------------
                 CC|                            |rob.fx907 at gmail.com

--- Comment #1 from Rob <rob.fx907 at gmail.com> ---
 (In reply to Graham Perrin from comment #0)

This is normal behavior, although the error message could be more descriptive.

One thing to remember is, bectl creates a snapshot behind the scenes when you
create a boot environment. A boot environment is cloned from the given
snapshot.

Here's a quick summary of your output, we can see that the 'r342851-with-locks'
boot environment is backed by the 'r343023 at 2019-01-14-17:49:17' snapshot. We
can also see that a snapshot was created from the 'r342851-with-locks' boot
environment, that snapshot is named 'r342851-with-locks at 2019-01-22-01:34:50'.
Looking at boot environment 'r342851',
we see that 'r342851' was created from snapshot
'r342851-with-locks at 2019-01-22-01:34:50'. The boot environment 'r342851'
is dependant on the snapshot it is created from,
'r342851-with-locks at 2019-01-22-01:34:50'.

You aren't able to destroy 'r342851-with-locks' because 'r342851' depends on
snapshot 'r342851-with-locks at 2019-01-22-01:34:50' which
depends on 'r342851-with-locks'. This means 'r342851' depends on
'r342851-with-locks'.


A better error message may be:

root at momh167-gjp4-8570p:~ # bectl destroy r342851-with-locks
cannot destroy 'r342851-with-locks': boot environment has dependent clones/boot
environments
    r342851

-- 
You are receiving this mail because:
You are the assignee for the bug.