1.\" 2.\" CDDL HEADER START 3.\" 4.\" The contents of this file are subject to the terms of the 5.\" Common Development and Distribution License (the "License"). 6.\" You may not use this file except in compliance with the License. 7.\" 8.\" You can obtain a copy of the license at usr/src/OPENSOLARIS.LICENSE 9.\" or http://www.opensolaris.org/os/licensing. 10.\" See the License for the specific language governing permissions 11.\" and limitations under the License. 12.\" 13.\" When distributing Covered Code, include this CDDL HEADER in each 14.\" file and include the License file at usr/src/OPENSOLARIS.LICENSE. 15.\" If applicable, add the following below this CDDL HEADER, with the 16.\" fields enclosed by brackets "[]" replaced with your own identifying 17.\" information: Portions Copyright [yyyy] [name of copyright owner] 18.\" 19.\" CDDL HEADER END 20.\" 21.\" 22.\" Copyright (c) 2009 Sun Microsystems, Inc. All Rights Reserved. 23.\" Copyright 2011 Joshua M. Clulow <josh@sysmgr.org> 24.\" Copyright (c) 2011, 2019 by Delphix. All rights reserved. 25.\" Copyright (c) 2013 by Saso Kiselkov. All rights reserved. 26.\" Copyright (c) 2014, Joyent, Inc. All rights reserved. 27.\" Copyright (c) 2014 by Adam Stevko. All rights reserved. 28.\" Copyright (c) 2014 Integros [integros.com] 29.\" Copyright 2019 Richard Laager. All rights reserved. 30.\" Copyright 2018 Nexenta Systems, Inc. 31.\" Copyright 2019 Joyent, Inc. 32.\" 33.Dd June 30, 2019 34.Dt ZFS-PROMOTE 8 35.Os 36.Sh NAME 37.Nm zfs Ns Pf - Cm promote 38.Nd Promotes a clone file system to no longer be dependent on its origin snapshot. 39.Sh SYNOPSIS 40.Nm 41.Cm promote 42.Ar clone-filesystem 43.Sh DESCRIPTION 44.Bl -tag -width "" 45.It Xo 46.Nm 47.Cm promote 48.Ar clone-filesystem 49.Xc 50The 51.Cm promote 52command makes it possible to destroy the file system that the clone was created 53from. 54The clone parent-child dependency relationship is reversed, so that the origin 55file system becomes a clone of the specified file system. 56.Pp 57The snapshot that was cloned, and any snapshots previous to this snapshot, are 58now owned by the promoted clone. 59The space they use moves from the origin file system to the promoted clone, so 60enough space must be available to accommodate these snapshots. 61No new space is consumed by this operation, but the space accounting is 62adjusted. 63The promoted clone must not have any conflicting snapshot names of its own. 64The 65.Xr zfs-rename 8 66subcommand can be used to rename any conflicting snapshots. 67.El 68.Sh SEE ALSO 69.Xr zfs-clone 8 70