Re: ZFS: destroying snapshots without compromising boot environments
On 28/03/2020 15:19, Allan Jude wrote: > You can try to destroy the snapshot, if it is the basis of a clone, then > you will get an error, that you'd need to destroy the BE first, so you > might decide to keep that snapshot. As long as you don't use the -R flag > to zfs destroy dataset@snapshot, it will not destroy the clones. > > You can also use 'zfs promote' to make the clone into the parent, making > the original parent into the clone. This allows you to destroy that > original and the snapshot while keeping the clone. Perfect, thank you. I was nervous about destruction without warning. Below, are the differences (in measurement) between beadm and bectl to be expected? root@momh167-gjp4-8570p:~ # beadm list BE Active Mountpoint Space Created Waterfox - - 15.9G 2020-03-10 18:24 r357746f - - 1.3G 2020-03-20 06:19 r359249b NR / 74.7G 2020-03-28 01:19 root@momh167-gjp4-8570p:~ # beadm list -aDs BE/Dataset/Snapshot Active Mountpoint Space Created Waterfox copperbowl/ROOT/Waterfox - - 137.0M 2020-03-10 18:24 r359249b@2020-03-17-21:57:17 - - 59.2G 2020-03-17 21:57 copperbowl/ROOT/Waterfox@2020-03-20-06:19:45 - - 67.0M 2020-03-20 06:19 r357746f copperbowl/ROOT/r357746f - - 1.2G 2020-03-20 06:19 Waterfox@2020-03-20-06:19:45 - - 59.2G 2020-03-20 06:19 r359249b copperbowl/ROOT/r359249b@2020-03-17-21:57:17 - - 15.7G 2020-03-17 21:57 copperbowl/ROOT/r359249b NR / 59.0G 2020-03-28 01:19 root@momh167-gjp4-8570p:~ # bectl list BE Active Mountpoint Space Created Waterfox - - 204M 2020-03-10 18:24 r357746f - - 1.21G 2020-03-20 06:19 r359249b NR / 74.7G 2020-03-28 01:19 root@momh167-gjp4-8570p:~ # bectl list -aDs BE/Dataset/Snapshot Active Mountpoint Space Created Waterfox copperbowl/ROOT/Waterfox - - 204M 2020-03-10 18:24 Waterfox@2020-03-20-06:19:45 - - 67.0M 2020-03-20 06:19 r357746f copperbowl/ROOT/r357746f - - 1.21G 2020-03-20 06:19 r359249b copperbowl/ROOT/r359249b NR / 74.7G 2020-03-28 01:19 r359249b@2020-03-17-21:57:17 - - 15.7G 2020-03-17 21:57 root@momh167-gjp4-8570p:~ # zfs list -t snapshot NAME USED AVAIL REFER MOUNTPOINT copperbowl/ROOT/Waterfox@2020-03-20-06:19:45 67.0M - 59.2G - copperbowl/ROOT/r359249b@2020-03-17-21:57:17 15.7G - 59.2G - copperbowl/iocage/releases/12.0-RELEASE/root@jbrowsers 8K - 1.24G - copperbowl/poudriere/jails/head@clean 328K - 1.89G - root@momh167-gjp4-8570p:~ # zfs destroy copperbowl/ROOT/r359249b@2020-03-17-21:57:17 cannot destroy 'copperbowl/ROOT/r359249b@2020-03-17-21:57:17': snapshot has dependent clones use '-R' to destroy the following datasets: copperbowl/ROOT/r357746f copperbowl/ROOT/Waterfox@2020-03-20-06:19:45 copperbowl/ROOT/Waterfox root@momh167-gjp4-8570p:~ # date ; uname -v Sat Mar 28 15:30:57 GMT 2020 FreeBSD 13.0-CURRENT #1 r359249: Tue Mar 24 00:12:27 GMT 2020 root@momh167-gjp4-8570p:/usr/obj/usr/src/amd64.amd64/sys/GENERIC-NODEBUG root@momh167-gjp4-8570p:~ # ___ freebsd-current@freebsd.org mailing list https://lists.freebsd.org/mailman/listinfo/freebsd-current To unsubscribe, send any mail to "freebsd-current-unsubscr...@freebsd.org"
Re: ZFS: destroying snapshots without compromising boot environments
On 2020-03-28 03:24, Graham Perrin wrote: > I imagine that some of the 2019 snapshots below are redundant. > > Can I safely destroy any of them? > > $ zfs list -t snapshot > NAME USED AVAIL > REFER MOUNTPOINT > copperbowl/ROOT/Waterfox@2020-03-20-06:19:45 67.0M - 59.2G - > copperbowl/ROOT/r359249b@2019-08-18-04:04:53 5.82G - 40.9G - > copperbowl/ROOT/r359249b@2019-08-18-11:28:31 4.32G - 40.7G - > copperbowl/ROOT/r359249b@2019-09-13-18:45:27-0 9.43G - 43.4G - > copperbowl/ROOT/r359249b@2019-09-19-20:03:26 5.13G - 43.3G - > copperbowl/ROOT/r359249b@2019-09-24-20:45:59-0 7.67G - 44.6G - > copperbowl/ROOT/r359249b@2020-01-09-17:05:57-0 7.66G - 55.2G - > copperbowl/ROOT/r359249b@2020-01-11-14:15:47 7.41G - 56.2G - > copperbowl/ROOT/r359249b@2020-03-17-21:57:17 12.0G - 59.2G - > copperbowl/iocage/releases/12.0-RELEASE/root@jbrowsers 8K - 1.24G - > copperbowl/poudriere/jails/head@clean 328K - 1.89G - > $ beadm list > BE Active Mountpoint Space Created > Waterfox - - 12.2G 2020-03-10 18:24 > r357746f - - 1.3G 2020-03-20 06:19 > r359249b NR / 148.9G 2020-03-28 01:19 > $ beadm list -aDs > BE/Dataset/Snapshot Active Mountpoint > Space Created > > Waterfox > copperbowl/ROOT/Waterfox - - 137.0M > 2020-03-10 18:24 > r359249b@2020-03-17-21:57:17 - - 59.2G > 2020-03-17 21:57 > copperbowl/ROOT/Waterfox@2020-03-20-06:19:45 - - 67.0M > 2020-03-20 06:19 > > r357746f > copperbowl/ROOT/r357746f - - 1.2G > 2020-03-20 06:19 > Waterfox@2020-03-20-06:19:45 - - 59.2G > 2020-03-20 06:19 > > r359249b > copperbowl/ROOT/r359249b@2019-08-18-04:04:53 - - 5.8G > 2019-08-18 04:04 > copperbowl/ROOT/r359249b@2019-08-18-11:28:31 - - 4.3G > 2019-08-18 11:28 > copperbowl/ROOT/r359249b@2019-09-13-18:45:27-0 - - 9.4G > 2019-09-13 18:45 > copperbowl/ROOT/r359249b@2019-09-19-20:03:26 - - 5.1G > 2019-09-19 20:03 > copperbowl/ROOT/r359249b@2019-09-24-20:45:59-0 - - 7.7G > 2019-09-24 20:45 > copperbowl/ROOT/r359249b@2020-01-09-17:05:57-0 - - 7.7G > 2020-01-09 17:05 > copperbowl/ROOT/r359249b@2020-01-11-14:15:47 - - 7.4G > 2020-01-11 14:15 > copperbowl/ROOT/r359249b@2020-03-17-21:57:17 - - 12.0G > 2020-03-17 21:57 > copperbowl/ROOT/r359249b NR / 59.0G > 2020-03-28 01:19 > $ > > ___ > freebsd-current@freebsd.org mailing list > https://lists.freebsd.org/mailman/listinfo/freebsd-current > To unsubscribe, send any mail to "freebsd-current-unsubscr...@freebsd.org" You can try to destroy the snapshot, if it is the basis of a clone, then you will get an error, that you'd need to destroy the BE first, so you might decide to keep that snapshot. As long as you don't use the -R flag to zfs destroy dataset@snapshot, it will not destroy the clones. You can also use 'zfs promote' to make the clone into the parent, making the original parent into the clone. This allows you to destroy that original and the snapshot while keeping the clone. -- Allan Jude signature.asc Description: OpenPGP digital signature
Re: ZFS: destroying snapshots without compromising boot environments
On Sat, Mar 28, 2020 at 10:30 AM Graham Perrin wrote: > > I imagine that some of the 2019 snapshots below are redundant. > > Can I safely destroy any of them? > > $ zfs list -t snapshot > NAME USED AVAIL > REFER MOUNTPOINT > copperbowl/ROOT/Waterfox@2020-03-20-06:19:4567.0M - 59.2G - > copperbowl/ROOT/r359249b@2019-08-18-04:04:535.82G - 40.9G - > copperbowl/ROOT/r359249b@2019-08-18-11:28:314.32G - 40.7G - > copperbowl/ROOT/r359249b@2019-09-13-18:45:27-0 9.43G - 43.4G - > copperbowl/ROOT/r359249b@2019-09-19-20:03:265.13G - 43.3G - > copperbowl/ROOT/r359249b@2019-09-24-20:45:59-0 7.67G - 44.6G - > copperbowl/ROOT/r359249b@2020-01-09-17:05:57-0 7.66G - 55.2G - > copperbowl/ROOT/r359249b@2020-01-11-14:15:477.41G - 56.2G - > copperbowl/ROOT/r359249b@2020-03-17-21:57:1712.0G - 59.2G - > copperbowl/iocage/releases/12.0-RELEASE/root@jbrowsers 8K - 1.24G - > copperbowl/poudriere/jails/head@clean328K - 1.89G - > $ beadm list > BE Active Mountpoint Space Created > Waterfox - - 12.2G 2020-03-10 18:24 > r357746f - -1.3G 2020-03-20 06:19 > r359249b NR / 148.9G 2020-03-28 01:19 > $ beadm list -aDs > BE/Dataset/Snapshot Active Mountpoint > Space Created > > Waterfox >copperbowl/ROOT/Waterfox - - 137.0M > 2020-03-10 18:24 > r359249b@2020-03-17-21:57:17 - - 59.2G > 2020-03-17 21:57 >copperbowl/ROOT/Waterfox@2020-03-20-06:19:45 - - 67.0M > 2020-03-20 06:19 > > r357746f >copperbowl/ROOT/r357746f - -1.2G > 2020-03-20 06:19 > Waterfox@2020-03-20-06:19:45 - - 59.2G > 2020-03-20 06:19 > > r359249b >copperbowl/ROOT/r359249b@2019-08-18-04:04:53 - -5.8G > 2019-08-18 04:04 >copperbowl/ROOT/r359249b@2019-08-18-11:28:31 - -4.3G > 2019-08-18 11:28 >copperbowl/ROOT/r359249b@2019-09-13-18:45:27-0 - -9.4G > 2019-09-13 18:45 >copperbowl/ROOT/r359249b@2019-09-19-20:03:26 - -5.1G > 2019-09-19 20:03 >copperbowl/ROOT/r359249b@2019-09-24-20:45:59-0 - -7.7G > 2019-09-24 20:45 >copperbowl/ROOT/r359249b@2020-01-09-17:05:57-0 - -7.7G > 2020-01-09 17:05 >copperbowl/ROOT/r359249b@2020-01-11-14:15:47 - -7.4G > 2020-01-11 14:15 >copperbowl/ROOT/r359249b@2020-03-17-21:57:17 - - 12.0G > 2020-03-17 21:57 >copperbowl/ROOT/r359249b NR / 59.0G > 2020-03-28 01:19 > $ beadm destroy ? ;) ___ freebsd-current@freebsd.org mailing list https://lists.freebsd.org/mailman/listinfo/freebsd-current To unsubscribe, send any mail to "freebsd-current-unsubscr...@freebsd.org"
ZFS: destroying snapshots without compromising boot environments
I imagine that some of the 2019 snapshots below are redundant. Can I safely destroy any of them? $ zfs list -t snapshot NAME USED AVAIL REFER MOUNTPOINT copperbowl/ROOT/Waterfox@2020-03-20-06:19:45 67.0M - 59.2G - copperbowl/ROOT/r359249b@2019-08-18-04:04:53 5.82G - 40.9G - copperbowl/ROOT/r359249b@2019-08-18-11:28:31 4.32G - 40.7G - copperbowl/ROOT/r359249b@2019-09-13-18:45:27-0 9.43G - 43.4G - copperbowl/ROOT/r359249b@2019-09-19-20:03:26 5.13G - 43.3G - copperbowl/ROOT/r359249b@2019-09-24-20:45:59-0 7.67G - 44.6G - copperbowl/ROOT/r359249b@2020-01-09-17:05:57-0 7.66G - 55.2G - copperbowl/ROOT/r359249b@2020-01-11-14:15:47 7.41G - 56.2G - copperbowl/ROOT/r359249b@2020-03-17-21:57:17 12.0G - 59.2G - copperbowl/iocage/releases/12.0-RELEASE/root@jbrowsers 8K - 1.24G - copperbowl/poudriere/jails/head@clean 328K - 1.89G - $ beadm list BE Active Mountpoint Space Created Waterfox - - 12.2G 2020-03-10 18:24 r357746f - - 1.3G 2020-03-20 06:19 r359249b NR / 148.9G 2020-03-28 01:19 $ beadm list -aDs BE/Dataset/Snapshot Active Mountpoint Space Created Waterfox copperbowl/ROOT/Waterfox - - 137.0M 2020-03-10 18:24 r359249b@2020-03-17-21:57:17 - - 59.2G 2020-03-17 21:57 copperbowl/ROOT/Waterfox@2020-03-20-06:19:45 - - 67.0M 2020-03-20 06:19 r357746f copperbowl/ROOT/r357746f - - 1.2G 2020-03-20 06:19 Waterfox@2020-03-20-06:19:45 - - 59.2G 2020-03-20 06:19 r359249b copperbowl/ROOT/r359249b@2019-08-18-04:04:53 - - 5.8G 2019-08-18 04:04 copperbowl/ROOT/r359249b@2019-08-18-11:28:31 - - 4.3G 2019-08-18 11:28 copperbowl/ROOT/r359249b@2019-09-13-18:45:27-0 - - 9.4G 2019-09-13 18:45 copperbowl/ROOT/r359249b@2019-09-19-20:03:26 - - 5.1G 2019-09-19 20:03 copperbowl/ROOT/r359249b@2019-09-24-20:45:59-0 - - 7.7G 2019-09-24 20:45 copperbowl/ROOT/r359249b@2020-01-09-17:05:57-0 - - 7.7G 2020-01-09 17:05 copperbowl/ROOT/r359249b@2020-01-11-14:15:47 - - 7.4G 2020-01-11 14:15 copperbowl/ROOT/r359249b@2020-03-17-21:57:17 - - 12.0G 2020-03-17 21:57 copperbowl/ROOT/r359249b NR / 59.0G 2020-03-28 01:19 $ ___ freebsd-current@freebsd.org mailing list https://lists.freebsd.org/mailman/listinfo/freebsd-current To unsubscribe, send any mail to "freebsd-current-unsubscr...@freebsd.org"
