Date: Tue, 31 Mar 2020 15:32:53 -0400 From: mike tancsa <mike@sentex.net> To: freebsd-fs <freebsd-fs@freebsd.org> Subject: zfs promote Message-ID: <c86e4b80-664d-1ebe-7f50-c59b3c78421d@sentex.net>
next in thread | raw e-mail | index | archive | help
Hi, While doing some VM tests, I was making heavy use of clones from my zfs server. (clones are a super cool handy feature!)... However, when we went live, I accidentally used a clone as the production file system. Now, I cannot delete those old snapshots. It seems zfs promote is what I want, but I just want to make sure it will fully work the way I want it to. The history I did was zfs snapshot nfs3zroot/cyclenet@clean3 zfs clone nfs3zroot/cyclenet@clean3 nfs3zroot/cyclenetlive zfs set mountpoint=/cyclenet/live nfs3zroot/cyclenetlive If I do a zfs promote nfs3zroot/cyclenetlive I can then do a zfs destroy nfs3zroot/cyclenet@clean3 safely right ? i.e. nfs3zroot/cyclenetlive will then not have any historical dependencies ? Also, how much impact on the disk IO will the promote command have ? Is it long like a scrub, or quick like a snapshot ? ---Mike
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?c86e4b80-664d-1ebe-7f50-c59b3c78421d>