Date: Tue, 22 Jan 2019 16:36:57 +0000 From: bugzilla-noreply@freebsd.org To: bugs@FreeBSD.org Subject: =?UTF-8?B?W0J1ZyAyMzUxMzJdIGJlY3RsIGRlc3Ryb3kg4oCmIGNhbm5vdCBk?= =?UTF-8?B?ZXN0cm95IOKApjogZGF0YXNldCBhbHJlYWR5IGV4aXN0cw==?= Message-ID: <bug-235132-227@https.bugs.freebsd.org/bugzilla/>
next in thread | raw e-mail | index | archive | help
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=3D235132 Bug ID: 235132 Summary: bectl destroy =E2=80=A6 cannot destroy =E2=80=A6: datas= et already exists Product: Base System Version: CURRENT Hardware: Any OS: Any Status: New Severity: Affects Only Me Priority: --- Component: bin Assignee: bugs@FreeBSD.org Reporter: grahamperrin@gmail.com <https://www.freebsd.org/cgi/man.cgi?query=3Dbectl&sektion=3D8&manpath=3DFr= eeBSD+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 norm= al.) 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=20 root@momh167-gjp4-8570p:~ # bectl list -s BE/Dataset/Snapshot Active Mountpoint Space Created r343023 copperbowl/ROOT/r343023 NR /=20=20= =20=20=20=20=20=20=20 34.3G 2019-01-14 17:49 r343023@2019-01-07 - -=20=20= =20=20=20=20=20=20=20 1.08M 2019-01-07 07:48 r343023@2019-01-07-07:53:37 - -=20=20= =20=20=20=20=20=20=20 1.07M 2019-01-07 07:53 r343023@2019-01-07-19:31:37 - -=20=20= =20=20=20=20=20=20=20 33.6M 2019-01-07 19:31 r343023@2019-01-14-17:49:17 - -=20=20= =20=20=20=20=20=20=20 5.56G 2019-01-14 17:49 r342851 copperbowl/ROOT/r342851 - -=20=20= =20=20=20=20=20=20=20 728K 2019-01-07 19:31 copperbowl/ROOT/r342851-with-locks@2019-01-22-01:34:50 - -=20=20= =20=20=20=20=20=20=20 1.01M 2019-01-22 01:34 r342851-with-locks copperbowl/ROOT/r342851-with-locks - -=20=20= =20=20=20=20=20=20=20 3.36G 2019-01-22 01:34 copperbowl/ROOT/r343023@2019-01-14-17:49:17 - -=20=20= =20=20=20=20=20=20=20 5.56G 2019-01-14 17:49 r342851-with-locks@2019-01-22-01:34:50 - -=20=20= =20=20=20=20=20=20=20 1.01M 2019-01-22 01:34 r342466 copperbowl/ROOT/r342466 - -=20=20= =20=20=20=20=20=20=20 1.13M 2019-01-07 07:53 copperbowl/ROOT/r343023@2019-01-07-19:31:37 - -=20=20= =20=20=20=20=20=20=20 33.6M 2019-01-07 19:31 default copperbowl/ROOT/default - -=20=20= =20=20=20=20=20=20=20 1.09M 2018-12-22 05:01 copperbowl/ROOT/r343023@2019-01-07-07:53:37 - -=20=20= =20=20=20=20=20=20=20 1.07M 2019-01-07 07:53 root@momh167-gjp4-8570p:~ # --=20 You are receiving this mail because: You are the assignee for the bug.=
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?bug-235132-227>