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

classic Classic list List threaded Threaded
3 messages Options
Reply | Threaded
Open this post in threaded view
|

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

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

            Bug ID: 235132
           Summary: bectl destroy … cannot destroy …: dataset already
                    exists
           Product: Base System
           Version: CURRENT
          Hardware: Any
                OS: Any
            Status: New
          Severity: Affects Only Me
          Priority: ---
         Component: bin
          Assignee: [hidden email]
          Reporter: [hidden email]

<https://www.freebsd.org/cgi/man.cgi?query=bectl&sektion=8&manpath=FreeBSD+13-current>

Below: is it normal for simple destruction, without specifying a snapshot, to
behave in this way? (Given the 'unknown error, I imagine that it's not normal.)

If it helps: I do not recall creating a snapshot.

TIA

----

root@momh167-gjp4-8570p:~ # bectl list
BE                 Active Mountpoint Space Created
r343023            NR     /          34.3G 2019-01-14 17:49
r342851            -      -          1.72M 2019-01-07 19:31
r342851-with-locks -      -          8.93G 2019-01-22 01:34
r342466            -      -          34.7M 2019-01-07 07:53
default            -      -          2.16M 2018-12-22 05:01
root@momh167-gjp4-8570p:~ # bectl destroy r342851-with-locks
cannot destroy 'copperbowl/ROOT/r342851-with-locks@2019-01-22-01:34:50':
dataset already exists
unknown error
root@momh167-gjp4-8570p:~ # date ; uname -v
Tue Jan 22 16:30:47 GMT 2019
FreeBSD 13.0-CURRENT r343023 GENERIC-NODEBUG
root@momh167-gjp4-8570p:~ # bectl list -s
BE/Dataset/Snapshot                                        Active Mountpoint
Space Created

r343023
  copperbowl/ROOT/r343023                                  NR     /        
34.3G 2019-01-14 17:49
  r343023@2019-01-07                                       -      -        
1.08M 2019-01-07 07:48
  r343023@2019-01-07-07:53:37                              -      -        
1.07M 2019-01-07 07:53
  r343023@2019-01-07-19:31:37                              -      -        
33.6M 2019-01-07 19:31
  r343023@2019-01-14-17:49:17                              -      -        
5.56G 2019-01-14 17:49

r342851
  copperbowl/ROOT/r342851                                  -      -        
728K  2019-01-07 19:31
    copperbowl/ROOT/r342851-with-locks@2019-01-22-01:34:50 -      -        
1.01M 2019-01-22 01:34

r342851-with-locks
  copperbowl/ROOT/r342851-with-locks                       -      -        
3.36G 2019-01-22 01:34
    copperbowl/ROOT/r343023@2019-01-14-17:49:17            -      -        
5.56G 2019-01-14 17:49
  r342851-with-locks@2019-01-22-01:34:50                   -      -        
1.01M 2019-01-22 01:34

r342466
  copperbowl/ROOT/r342466                                  -      -        
1.13M 2019-01-07 07:53
    copperbowl/ROOT/r343023@2019-01-07-19:31:37            -      -        
33.6M 2019-01-07 19:31

default
  copperbowl/ROOT/default                                  -      -        
1.09M 2018-12-22 05:01
    copperbowl/ROOT/r343023@2019-01-07-07:53:37            -      -        
1.07M 2019-01-07 07:53
root@momh167-gjp4-8570p:~ #

--
You are receiving this mail because:
You are the assignee for the bug.
_______________________________________________
[hidden email] mailing list
https://lists.freebsd.org/mailman/listinfo/freebsd-bugs
To unsubscribe, send any mail to "[hidden email]"
Reply | Threaded
Open this post in threaded view
|

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

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

Rob <[hidden email]> changed:

           What    |Removed                     |Added
----------------------------------------------------------------------------
                 CC|                            |[hidden email]

--- Comment #1 from Rob <[hidden email]> ---
 (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@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@2019-01-22-01:34:50'.
Looking at boot environment 'r342851',
we see that 'r342851' was created from snapshot
'r342851-with-locks@2019-01-22-01:34:50'. The boot environment 'r342851'
is dependant on the snapshot it is created from,
'r342851-with-locks@2019-01-22-01:34:50'.

You aren't able to destroy 'r342851-with-locks' because 'r342851' depends on
snapshot 'r342851-with-locks@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@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.
_______________________________________________
[hidden email] mailing list
https://lists.freebsd.org/mailman/listinfo/freebsd-bugs
To unsubscribe, send any mail to "[hidden email]"
Reply | Threaded
Open this post in threaded view
|

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

bugzilla-noreply
In reply to this post by bugzilla-noreply
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=235132

Kyle Evans <[hidden email]> changed:

           What    |Removed                     |Added
----------------------------------------------------------------------------
           Assignee|[hidden email]            |[hidden email]
                 CC|                            |[hidden email]

--- Comment #2 from Kyle Evans <[hidden email]> ---
Take

--
You are receiving this mail because:
You are the assignee for the bug.
_______________________________________________
[hidden email] mailing list
https://lists.freebsd.org/mailman/listinfo/freebsd-bugs
To unsubscribe, send any mail to "[hidden email]"