beadm no longer able to destroy, maybe since using OpenZFS

Graham Perrin grahamperrin at gmail.com
Sun May 3 05:05:35 UTC 2020


After reverting from OpenZFS to ZFS, I was able to destroy two of the 
boot environments that previously (below, 1st May, OpenZFS) could not be 
destroyed.

I'm left with at least one BE 'r360237c' that can not be destroyed. Is 
it ever normal to find a snapshot described as '-'?

root at momh167-gjp4-8570p:~ # kldstat | grep zfs
  2    1 0xffffffff82109000   3a8b40 zfs.ko
root at momh167-gjp4-8570p:~ # date
Sun May  3 05:59:06 BST 2020
root at momh167-gjp4-8570p:~ # beadm list -as
BE/Dataset/Snapshot                            Active Mountpoint Space 
Created

Waterfox
   copperbowl/ROOT/Waterfox                     -      - 314.0M 
2020-03-10 18:24
     r360237c at 2020-03-20-06:19:45               -      - 1.0G 2020-03-20 
06:19

r357746h
   copperbowl/ROOT/r357746h                     -      - 3.4M 2020-04-08 
09:28
     r360237c at 2020-04-09-17:59:32               -      - 1.1G 2020-04-09 
17:59

r360237c
   copperbowl/ROOT/r360237c at 2020-03-20-06:19:45 -      - 1.0G 2020-03-20 
06:19
   copperbowl/ROOT/r360237c at 2020-04-09-17:59:32 -      - 1.1G 2020-04-09 
17:59
   copperbowl/ROOT/r360237c at 2020-04-29-13:24:52 -      - 11.2M 
2020-04-29 13:24
   copperbowl/ROOT/r360237c                     -      - 80.4G 
2020-04-29 13:24

r360237e
   copperbowl/ROOT/r360237e at 2020-05-01-17:58:33 -      - 96.6M 
2020-05-01 17:58
   copperbowl/ROOT/r360237e                     NR     / 1.3G 2020-05-01 
17:58
     r360237c at 2020-04-29-13:24:52               -      - 11.2M 
2020-04-29 13:24
root at momh167-gjp4-8570p:~ # beadm destroy r360237c
Are you sure you want to destroy 'r360237c'?
This action cannot be undone (y/[n]): y
Boot environment 'r360237c' was created from existing snapshot
Destroy '-' snapshot? (y/[n]): y
cannot destroy 'copperbowl/ROOT/r360237c': filesystem has dependent clones
use '-R' to destroy the following datasets:
copperbowl/ROOT/r360237e at 2020-05-01-17:58:33
copperbowl/ROOT/r360237e
copperbowl/ROOT/r357746h
copperbowl/ROOT/Waterfox
root at momh167-gjp4-8570p:~ # zfs list -t snapshot
NAME                                                     USED AVAIL  
REFER  MOUNTPOINT
copperbowl/ROOT/r360237c at 2020-03-20-06:19:45            1.02G -  59.2G  -
copperbowl/ROOT/r360237c at 2020-04-09-17:59:32            1.15G -  60.0G  -
copperbowl/ROOT/r360237c at 2020-04-29-13:24:52            11.2M -  62.2G  -
copperbowl/ROOT/r360237e at 2020-05-01-17:58:33            96.6M -  62.3G  -
copperbowl/iocage/releases/12.0-RELEASE/root at jbrowsers     8K -  1.24G  -
copperbowl/poudriere/jails/head at clean                    376K -  1.91G  -
copperbowl/usr/home at 2020-05-03-05:55-r360237            57.7M -   171G  -
root at momh167-gjp4-8570p:~ # uname -v
FreeBSD 13.0-CURRENT #54 r360237: Fri Apr 24 09:10:37 BST 2020 
root at momh167-gjp4-8570p:/usr/obj/usr/src/amd64.amd64/sys/GENERIC-NODEBUG
root at momh167-gjp4-8570p:~ #

----

On 01/05/2020 18:57, Graham Perrin wrote:
> root at momh167-gjp4-8570p:~ # date ; uname -v
> Fri May  1 18:52:31 BST 2020
> FreeBSD 13.0-CURRENT #54 r360237: Fri Apr 24 09:10:37 BST 2020 
> root at momh167-gjp4-8570p:/usr/obj/usr/src/amd64.amd64/sys/GENERIC-NODEBUG
> root at momh167-gjp4-8570p:~ # beadm list
> BE       Active Mountpoint  Space Created
> Waterfox -      -            1.3G 2020-03-10 18:24
> r357746h -      -          928.4M 2020-04-08 09:28
> r360237b -      -          213.6M 2020-04-28 20:17
> r360237c -      -           92.0G 2020-04-29 13:24
> r360237d -      -          153.2M 2020-04-30 13:08
> r360237e NR     /          720.4M 2020-05-01 17:58
> root at momh167-gjp4-8570p:~ # beadm destroy r360237b
> Are you sure you want to destroy 'r360237b'?
> This action cannot be undone (y/[n]): y
> cannot promote 'copperbowl/ROOT/r360237d': not a cloned filesystem
> root at momh167-gjp4-8570p:~ # beadm destroy r360237c
> Are you sure you want to destroy 'r360237c'?
> This action cannot be undone (y/[n]): y
> Boot environment 'r360237c' was created from existing snapshot
> Destroy '-' snapshot? (y/[n]): y
> cannot destroy 'copperbowl/ROOT/r360237c': filesystem has dependent 
> clones
> use '-R' to destroy the following datasets:
> copperbowl/ROOT/r360237e
> copperbowl/ROOT/r360237d at 2020-05-01-17:58:54
> copperbowl/ROOT/r360237d at 2020-05-01-17:58:33
> copperbowl/ROOT/r360237d
> copperbowl/ROOT/r360237b at 2020-04-30-13:08:36
> copperbowl/ROOT/r360237b
> copperbowl/ROOT/r357746h
> copperbowl/ROOT/Waterfox
> root at momh167-gjp4-8570p:~ # beadm destroy r360237d
> Are you sure you want to destroy 'r360237d'?
> This action cannot be undone (y/[n]): y
> cannot promote 'copperbowl/ROOT/r360237e': not a cloned filesystem
> root at momh167-gjp4-8570p:~ # beadm list -as
> BE/Dataset/Snapshot                            Active Mountpoint Space 
> Created
>
> Waterfox
>   copperbowl/ROOT/Waterfox                     -      - 314.0M 
> 2020-03-10 18:24
>     r360237c at 2020-03-20-06:19:45               -      - 1.0G 
> 2020-03-20 06:19
>
> r357746h
>   copperbowl/ROOT/r357746h                     -      - 3.4M 
> 2020-04-08 09:28
>     r360237c at 2020-04-09-17:59:32               -      - 925.0M 
> 2020-04-09 17:59
>
> r360237b
>   copperbowl/ROOT/r360237b                     -      - 202.4M 
> 2020-04-28 20:17
>     r360237c at 2020-04-29-13:24:52               -      - 11.2M 
> 2020-04-29 13:24
>   copperbowl/ROOT/r360237b at 2020-04-30-13:08:36 -      - 1.4M 
> 2020-04-30 13:08
>
> r360237c
>   copperbowl/ROOT/r360237c at 2020-03-20-06:19:45 -      - 1.0G 
> 2020-03-20 06:19
>   copperbowl/ROOT/r360237c at 2020-04-09-17:59:32 -      - 925.0M 
> 2020-04-09 17:59
>   copperbowl/ROOT/r360237c at 2020-04-20-06:44:01 -      - 11.6G 
> 2020-04-20 06:44
>   copperbowl/ROOT/r360237c at 2020-04-29-13:24:52 -      - 11.2M 
> 2020-04-29 13:24
>   copperbowl/ROOT/r360237c                     -      - 92.0G 
> 2020-04-29 13:24
>
> r360237d
>   copperbowl/ROOT/r360237d                     -      - 151.8M 
> 2020-04-30 13:08
>     r360237b at 2020-04-30-13:08:36               -      - 1.4M 
> 2020-04-30 13:08
>   copperbowl/ROOT/r360237d at 2020-05-01-17:58:33 -      - 440.0K 
> 2020-05-01 17:58
>   copperbowl/ROOT/r360237d at 2020-05-01-17:58:54 -      - 408.0K 
> 2020-05-01 17:58
>
> r360237e
>   copperbowl/ROOT/r360237e                     NR     / 720.0M 
> 2020-05-01 17:58
>     r360237d at 2020-05-01-17:58:54               -      - 408.0K 
> 2020-05-01 17:58
> root at momh167-gjp4-8570p:~ # zfs list -t snapshot
> NAME                                                     USED AVAIL  
> REFER  MOUNTPOINT
> copperbowl/ROOT/r360237b at 2020-04-30-13:08:36            1.36M - 62.3G  -
> copperbowl/ROOT/r360237c at 2020-03-20-06:19:45            1.02G - 59.2G  -
> copperbowl/ROOT/r360237c at 2020-04-09-17:59:32             925M - 60.0G  -
> copperbowl/ROOT/r360237c at 2020-04-20-06:44:01            11.6G - 61.7G  -
> copperbowl/ROOT/r360237c at 2020-04-29-13:24:52            11.2M - 62.2G  -
> copperbowl/ROOT/r360237d at 2020-05-01-17:58:33             440K - 62.3G  -
> copperbowl/ROOT/r360237d at 2020-05-01-17:58:54             408K - 62.3G  -
> copperbowl/iocage/releases/12.0-RELEASE/root at jbrowsers     8K - 1.24G  -
> copperbowl/poudriere/jails/head at clean                    384K - 1.91G  -
> copperbowl/usr/home at 2020-04-28-10:42-r360237            5.89G - 172G  -
> root at momh167-gjp4-8570p:~ #
>


More information about the freebsd-current mailing list