I had a zpool and was using the implicit zfs filesystem in it:
data 10.2G 124G 8.53G /var/tellme
d...@hotbackup.h23 83.4M - 8.52G -
d...@hotbackup.h00 25.9M - 8.52G -
d...@hotbackup.h01 16.2M - 8.52G -
...
These contained hourly zfs snapshots that I preferred to preserve.
However, I was also trying to convert this to follow our standard naming,
which meant that this filesystem should have been called data/var_tellme.
I ran the following:
# zfs snapshot d...@clean
# zfs clone d...@clean data/var_tellme
# zfs promote data/var_tellme
This worked as expected and now I have:
NAME USED AVAIL REFER MOUNTPOINT
data 9.70G 124G 8.53G legacy
data/var_tellme 9.70G 124G 8.10G legacy
data/var_tel...@clean 717M - 8.53G -
data/var_tel...@hotbackup.h14 24.4M - 8.09G -
data/var_tel...@hotbackup.h15 10.0M - 8.09G -
data/var_tel...@hotbackup.h16 6.14M - 8.09G -
...
However, now I cannot remove the data/var_tel...@clean snapshot because it
is now labelled as the 'origin' for data itself:
# zfs get origin data
NAME PROPERTY VALUE SOURCE
data origin data/var_tel...@clean -
I don't care about the 'data' filesystem anymore, I just want to be able
to nuke the data/var_tel...@clean snapshot so it doesn't end up filling my
zpool with changes.
Any thoughts on how this can be done? I do have other systems I can use
to test this procedure, but ideally it would not introduce any downtime,
but that can be arranged if necessary.
Thanks,
Todd
_______________________________________________
zfs-discuss mailing list
zfs-discuss@opensolaris.org
http://mail.opensolaris.org/mailman/listinfo/zfs-discuss
