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

[bugzilla-noreply at freebsd.org]

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: bugs at FreeBSD.org
          Reporter: grahamperrin at gmail.com

<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 at 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 at momh167-gjp4-8570p:~ # bectl destroy r342851-with-locks
cannot destroy 'copperbowl/ROOT/r342851-with-locks at 2019-01-22-01:34:50':
dataset already exists
unknown error
root at momh167-gjp4-8570p:~ # date ; uname -v
Tue Jan 22 16:30:47 GMT 2019
FreeBSD 13.0-CURRENT r343023 GENERIC-NODEBUG 
root at 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 at 2019-01-07                                       -      -         
1.08M 2019-01-07 07:48
  r343023 at 2019-01-07-07:53:37                              -      -         
1.07M 2019-01-07 07:53
  r343023 at 2019-01-07-19:31:37                              -      -         
33.6M 2019-01-07 19:31
  r343023 at 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 at 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 at 2019-01-14-17:49:17            -      -         
5.56G 2019-01-14 17:49
  r342851-with-locks at 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 at 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 at 2019-01-07-07:53:37            -      -         
1.07M 2019-01-07 07:53
root at momh167-gjp4-8570p:~ #

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