From sacadmin Sat May 6 00:06:27 2006 Received: from cathy.eng.sun.com (cathy.SFBay.Sun.COM [129.146.228.63]) by sac.sfbay.sun.com (8.12.9+Sun/8.12.9) with ESMTP id k4676RIQ003237; Sat, 6 May 2006 00:06:27 -0700 (PDT) Received: from cathy.eng.sun.com (localhost [127.0.0.1]) by cathy.eng.sun.com (8.13.6+Sun/8.13.6) with ESMTP id k4676PBs152100; Sat, 6 May 2006 00:06:25 -0700 (PDT) Received: (from bonwick@localhost) by cathy.eng.sun.com (8.13.6+Sun/8.13.6/Submit) id k4676PqA152085; Sat, 6 May 2006 00:06:25 -0700 (PDT) Date: Sat, 6 May 2006 00:06:25 -0700 (PDT) From: Jeff Bonwick Message-Id: <200605060706.k4676PqA152085@cathy.eng.sun.com> To: PSARC@sac.sfbay.sun.com Cc: jeff.bonwick@sun.com, matthew.ahrens@sun.com Subject: ZFS Clone Promotion [PSARC/2006/303 Timeout: 05/12/2006] Status: RO Content-Length: 4204 Subject: PSARC FastTrack [05/12/2006]: ZFS Clone Promotion Template Version: @(#)sac_nextcase 1.56 10/26/05 SMI Copyright 2006 Sun Microsystems, Inc. 1. Introduction 1.1. Project/Component Working Name: ZFS Clone Promotion 1.2. Name of Document Author/Supplier: Author: Matt Ahrens 1.3 Date of This Document: 06 May, 2006 4. Technical Description ZFS provides the ability to create read-only snapshots of any filesystem, and to create writeable clones of any snapshot. Suppose that F is a filesystem, S is a snapshot of F, and C is a clone of S. Topologically, F and C are peers: that is, S is a common origin point from which F and C diverge. F and C differ only in how their space is accounted and where they appear in the namespace. After using a clone to explore some alternate reality (e.g. to test a patch), it's often desirable to 'promote' the clone to 'main' filesystem status -- that is, to swap F and C in the namespace. This is what 'zfs promote' does. Here are man page changes: in the SYNOPSIS section (after 'zfs clone'): > zfs promote in the DESCRIPTION - Clones section (only last paragraph is added): Clones A clone is a writable volume or file system whose initial contents are the same as another dataset. As with snapshots, creating a clone is nearly instantaneous, and initially con- sumes no additional space. Clones can only be created from a snapshot. When a snapshot is cloned, it creates an implicit dependency between the parent and child. Even though the clone is created somewhere else in the dataset hierarchy, the original snapshot cannot be destroyed as long as a clone exists. The "origin" pro- perty exposes this dependency, and the destroy command lists any such dependencies, if they exist. > The clone parent-child dependency relationship can be reversed by > using the _promote_ subcommand. This causes the "origin" > filesystem to become a clone of the specified filesystem, which > makes it possible to destroy the filesystem that the clone was > created from. in the SUBCOMMANDS section (after 'zfs clone'): > zfs promote > > Promotes a clone filesystem to no longer be dependent on its > "origin" snapshot. This makes it possible to destroy the > filesystem that the clone was created from. The dependency > relationship is reversed, so that the "origin" filesystem > becomes a clone of the specified filesystem. > > The snaphot that was cloned, and any snapshots previous to this > snapshot will now be owned by the promoted clone. The space > they use will move from the "origin" filesystem to the promoted > clone, so is must have enough space available to accommodate > these snapshots. Note: no new space is consumed by this > operation, but the space accounting is adjusted. Also note that > the promoted clone must not have any conflicting snapshot names > of its own. The _rename_ subcommand can be used to rename any > conflicting snapshots. in the EXAMPLES section (after 'Example 8: Creating a clone'): > Example 9: Promoting a Clone > > The following commands illustrate how to test out changes to a > filesystem, and then replace the original filesystem with the > changed one, using clones, clone promotion, and renaming. > > # zfs create pool/project/production > > # zfs snapshot pool/project/production@today > # zfs clone pool/project/production@today pool/project/beta > > # zfs promote pool/project/beta > # zfs rename pool/project/production pool/project/legacy > # zfs rename pool/project/beta pool/project/production > destroyed> > # zfs destroy pool/project/legacy 6. Resources and Schedule 6.4. Steering Committee requested information 6.4.1. Consolidation C-team Name: ON 6.5. ARC review type: FastTrack From sacadmin Tue May 9 02:23:31 2006 Received: from sunmail3.sfbay.sun.com (sunmail3.SFBay.Sun.COM [129.149.247.180]) by sac.sfbay.sun.com (8.12.9+Sun/8.12.9) with ESMTP id k499NUIQ000935 for ; Tue, 9 May 2006 02:23:31 -0700 (PDT) Received: from brm-avmta-1.central.sun.com (brm-avmta-1.Central.Sun.COM [129.147.4.11]) by sunmail3.sfbay.sun.com (8.11.7p1+Sun/8.11.7/ENSMAIL,v2.2) with ESMTP id k499NUw25596 for <@sunmail1brm.central.sun.com:psarc@Sun.COM>; Tue, 9 May 2006 02:23:30 -0700 (PDT) Received: from pmxchannel-daemon.brm-avmta-1.central.sun.com by brm-avmta-1.central.sun.com (Sun Java System Messaging Server 6.2-3.04 (built Jul 15 2005)) id <0IYZ00J09RF4KX00@brm-avmta-1.central.sun.com> for psarc@Sun.COM (ORCPT psarc@Sun.COM); Tue, 09 May 2006 03:23:28 -0600 (MDT) Received: from nis-uk.uk.sun.com ([129.156.85.41]) by brm-avmta-1.central.sun.com (Sun Java System Messaging Server 6.2-3.04 (built Jul 15 2005)) with ESMTP id <0IYZ001MHRF3R7C0@brm-avmta-1.central.sun.com> for psarc@Sun.COM (ORCPT psarc@Sun.COM); Tue, 09 May 2006 03:23:28 -0600 (MDT) Received: from enospc.uk.sun.com (enospc [129.156.173.14]) by nis-uk.uk.sun.com (8.12.10+Sun/8.12.10/ENSMAIL,v2.2) with ESMTP id k499NQoR012892; Tue, 09 May 2006 10:23:26 +0100 (BST) Received: from [129.150.120.102] (vpn-129-150-120-102.UK.Sun.COM [129.150.120.102]) by enospc.uk.sun.com (8.13.4+Sun/8.13.3/CTE 3.0) with ESMTP id k499NOBM014714; Tue, 09 May 2006 10:23:25 +0100 (BST) Date: Tue, 09 May 2006 10:22:59 +0100 From: Darren J Moffat Subject: PSARC/2006/303 ZFS clone promotion To: Jeff.Bonwick@Sun.COM, psarc@Sun.COM Message-id: <44605F73.7060105@Sun.COM> MIME-version: 1.0 Content-type: text/plain; charset=ISO-8859-1; format=flowed Content-transfer-encoding: 7BIT X-PMX-Version: 5.1.2.240295 User-Agent: Thunderbird 1.5 (X11/20060113) Status: RO Content-Length: 681 I'm assuming this applies to zvol as well - I'm sure it does since the docs doesn't say that it doesn't apply. Now for my real questions... Does promoting a clone that is shared via NFS have any impact on the clients ? I assume not but for some reason that I'm not sure about my head is telling me to ask this. I'm assuming also that the data set identified in the DSL doesn't change as a result of this (or a rename) operation right ? The man page text says that there must not be any conflicting snapshot names, I'm assuming that a sensible "you have the following conflicting snapshots:" message will be given if the attempt is made to promote ? -- Darren J Moffat From sacadmin Tue May 9 13:45:30 2006 Received: from sunmail4.Singapore.Sun.COM (sunmail4.Singapore.Sun.COM [129.158.71.19]) by sac.sfbay.sun.com (8.13.6+Sun/8.13.6) with ESMTP id k49KjThK026811 for ; Tue, 9 May 2006 13:45:30 -0700 (PDT) Received: from nwk-avmta-2.sfbay.sun.com (nwk-avmta-2.SFBay.Sun.COM [129.149.247.22]) by sunmail4.Singapore.Sun.COM (8.13.4+Sun/8.13.3/ENSMAIL,v2.2) with ESMTP id k49Kj7uP011777 for <@sunmail3.sfbay.sun.com:psarc@Sun.COM>; Wed, 10 May 2006 04:45:28 +0800 (SGT) Received: from pmxchannel-daemon.nwk-avmta-2.sfbay.sun.com by nwk-avmta-2.sfbay.sun.com (Sun Java System Messaging Server 6.2-3.04 (built Jul 15 2005)) id <0IZ000C01MZSYZ00@nwk-avmta-2.sfbay.sun.com> for psarc@Sun.COM (ORCPT psarc@Sun.COM); Tue, 09 May 2006 13:45:28 -0700 (PDT) Received: from sfbaymail1sca.SFBay.Sun.COM ([129.145.154.35]) by nwk-avmta-2.sfbay.sun.com (Sun Java System Messaging Server 6.2-3.04 (built Jul 15 2005)) with ESMTP id <0IZ0007K4MZSA430@nwk-avmta-2.sfbay.sun.com> for psarc@Sun.COM (ORCPT psarc@Sun.COM); Tue, 09 May 2006 13:45:28 -0700 (PDT) Received: from pacifica.sfbay.sun.com (pacifica.SFBay.Sun.COM [129.146.228.204]) by sfbaymail1sca.SFBay.Sun.COM (8.12.10+Sun/8.12.10/ENSMAIL,v2.2) with ESMTP id k49KjQoc009563; Tue, 09 May 2006 13:45:26 -0700 (PDT) Received: from pacifica.sfbay.sun.com (localhost [127.0.0.1]) by pacifica.sfbay.sun.com (8.13.5+Sun/8.13.5) with ESMTP id k49KguY6205157; Tue, 09 May 2006 13:42:56 -0700 (PDT) Received: (from ahrens@localhost) by pacifica.sfbay.sun.com (8.13.5+Sun/8.13.5/Submit) id k49KgusS205156; Tue, 09 May 2006 13:42:56 -0700 (PDT) Date: Tue, 09 May 2006 13:42:56 -0700 From: Matthew Ahrens Subject: Re: PSARC/2006/303 ZFS clone promotion To: Jeff.Bonwick@Sun.COM, psarc@Sun.COM, Darren.Moffat@Sun.COM Message-id: <20060509204256.GF185493@eng.sun.com> MIME-version: 1.0 Content-type: text/plain; charset=us-ascii Content-transfer-encoding: 7BIT Content-disposition: inline X-PMX-Version: 5.1.2.240295 User-Agent: Mutt/1.4.2.1i Status: RO Content-Length: 557 Yes, this applies to any cloned datasets, including clones of zvols. The only real NFS-visible change as a result of 'zfs promote' is the renaming of the snapshots from the clone origin filesystem to the cloned filesystem. If you are accessing the snapshot via NFS, it will be renamed out from under you, and the client will get a "no such file or directory" error. No dataset IDs change as a result of this operation. Yes, if there is a conflicting snapshot name, we print a nice error message (including the name of the conflicting snapshot). --matt From sacadmin Tue May 9 14:09:17 2006 Received: from sunmail4.Singapore.Sun.COM (sunmail4.Singapore.Sun.COM [129.158.71.19]) by sac.sfbay.sun.com (8.13.6+Sun/8.13.6) with ESMTP id k49L9Giw028465 for ; Tue, 9 May 2006 14:09:17 -0700 (PDT) Received: from nwk-avmta-2.sfbay.sun.com (nwk-avmta-2.SFBay.Sun.COM [129.149.247.22]) by sunmail4.Singapore.Sun.COM (8.13.4+Sun/8.13.3/ENSMAIL,v2.2) with ESMTP id k49L8xUN026041; Wed, 10 May 2006 05:09:12 +0800 (SGT) Received: from pmxchannel-daemon.nwk-avmta-2.sfbay.sun.com by nwk-avmta-2.sfbay.sun.com (Sun Java System Messaging Server 6.2-3.04 (built Jul 15 2005)) id <0IZ000E0VO39KU00@nwk-avmta-2.sfbay.sun.com>; Tue, 09 May 2006 14:09:09 -0700 (PDT) Received: from jurassic.eng.sun.com ([129.146.56.144]) by nwk-avmta-2.sfbay.sun.com (Sun Java System Messaging Server 6.2-3.04 (built Jul 15 2005)) with ESMTP id <0IZ00079UO389Q40@nwk-avmta-2.sfbay.sun.com>; Tue, 09 May 2006 14:09:08 -0700 (PDT) Received: from sheplap.central.sun.com (sheplap.Central.Sun.COM [10.1.194.251]) by jurassic.eng.sun.com (8.13.6+Sun/8.13.6) with ESMTP id k49L985U749634; Tue, 09 May 2006 14:09:08 -0700 (PDT) Received: by sheplap.central.sun.com (Postfix, from userid 76367) id 2243321D9D4; Tue, 09 May 2006 16:09:25 -0500 (CDT) Date: Tue, 09 May 2006 16:09:25 -0500 From: Spencer Shepler Subject: Re: PSARC/2006/303 ZFS clone promotion In-reply-to: <20060509204256.GF185493@eng.sun.com> To: Matthew Ahrens Cc: Jeff.Bonwick@sun.com, psarc@sun.com, Darren.Moffat@sun.com Reply-to: spencer.shepler@sun.com Message-id: <20060509210925.GH9366@sheplap.central.sun.com> MIME-version: 1.0 Content-type: text/plain; charset=us-ascii Content-transfer-encoding: 7BIT Content-disposition: inline X-PMX-Version: 5.1.2.240295 References: <20060509204256.GF185493@eng.sun.com> User-Agent: Mutt/1.4.2.1i Status: RO Content-Length: 682 On Tue, Matthew Ahrens wrote: > Yes, this applies to any cloned datasets, including clones of zvols. > > The only real NFS-visible change as a result of 'zfs promote' is the > renaming of the snapshots from the clone origin filesystem to the cloned > filesystem. If you are accessing the snapshot via NFS, it will be > renamed out from under you, and the client will get a "no such file or > directory" error. The filehandle changes or the path changes. > > No dataset IDs change as a result of this operation. Is this my answer? > > Yes, if there is a conflicting snapshot name, we print a nice error > message (including the name of the conflicting snapshot). > > --matt From sacadmin Tue May 9 14:27:03 2006 Received: from sunmail3.sfbay.sun.com (sunmail3.SFBay.Sun.COM [129.149.247.180]) by sac.sfbay.sun.com (8.13.6+Sun/8.13.6) with ESMTP id k49LR3g0029242 for ; Tue, 9 May 2006 14:27:03 -0700 (PDT) Received: from brm-avmta-1.central.sun.com (brm-avmta-1.Central.Sun.COM [129.147.4.11]) by sunmail3.sfbay.sun.com (8.11.7p1+Sun/8.11.7/ENSMAIL,v2.2) with ESMTP id k49LR2w28502 for <@sunmail1brm.central.sun.com:psarc@sun.com>; Tue, 9 May 2006 14:27:02 -0700 (PDT) Received: from pmxchannel-daemon.brm-avmta-1.central.sun.com by brm-avmta-1.central.sun.com (Sun Java System Messaging Server 6.2-3.04 (built Jul 15 2005)) id <0IZ000303OX19B00@brm-avmta-1.central.sun.com> for psarc@sun.com (ORCPT psarc@sun.com); Tue, 09 May 2006 15:27:01 -0600 (MDT) Received: from sfbaymail1sca.SFBay.Sun.COM ([129.145.154.35]) by brm-avmta-1.central.sun.com (Sun Java System Messaging Server 6.2-3.04 (built Jul 15 2005)) with ESMTP id <0IZ000I9JOX0PPE0@brm-avmta-1.central.sun.com> for psarc@sun.com (ORCPT psarc@sun.com); Tue, 09 May 2006 15:27:01 -0600 (MDT) Received: from pacifica.sfbay.sun.com (pacifica.SFBay.Sun.COM [129.146.228.204]) by sfbaymail1sca.SFBay.Sun.COM (8.12.10+Sun/8.12.10/ENSMAIL,v2.2) with ESMTP id k49LQxoc003098; Tue, 09 May 2006 14:26:59 -0700 (PDT) Received: from pacifica.sfbay.sun.com (localhost [127.0.0.1]) by pacifica.sfbay.sun.com (8.13.5+Sun/8.13.5) with ESMTP id k49LOTSa205218; Tue, 09 May 2006 14:24:29 -0700 (PDT) Received: (from ahrens@localhost) by pacifica.sfbay.sun.com (8.13.5+Sun/8.13.5/Submit) id k49LOTkF205217; Tue, 09 May 2006 14:24:29 -0700 (PDT) Date: Tue, 09 May 2006 14:24:29 -0700 From: Matthew Ahrens Subject: Re: PSARC/2006/303 ZFS clone promotion In-reply-to: <20060509210925.GH9366@sheplap.central.sun.com> To: Spencer Shepler Cc: Jeff.Bonwick@sun.com, psarc@sun.com, Darren.Moffat@sun.com Message-id: <20060509212429.GJ185493@eng.sun.com> MIME-version: 1.0 Content-type: text/plain; charset=us-ascii Content-transfer-encoding: 7BIT Content-disposition: inline X-PMX-Version: 5.1.2.240295 References: <20060509204256.GF185493@eng.sun.com> <20060509210925.GH9366@sheplap.central.sun.com> User-Agent: Mutt/1.4.2.1i Status: RO Content-Length: 1037 On Tue, May 09, 2006 at 04:09:25PM -0500, Spencer Shepler wrote: > On Tue, Matthew Ahrens wrote: > > Yes, this applies to any cloned datasets, including clones of zvols. > > > > The only real NFS-visible change as a result of 'zfs promote' is the > > renaming of the snapshots from the clone origin filesystem to the cloned > > filesystem. If you are accessing the snapshot via NFS, it will be > > renamed out from under you, and the client will get a "no such file or > > directory" error. > > The filehandle changes or the path changes. The filehandle changes, since the fsid of a snapshot is tied to its containing filesystem. This is essentially the same as what happens locally, since the snapshot's (hidden) mountpoint goes away and is remounted elsewhere. > > No dataset IDs change as a result of this operation. > > Is this my answer? Sorry, this was in answer to Darren's question: > I'm assuming also that the data set identified in the DSL doesn't > change as a result of this (or a rename) operation right ? --matt From sacadmin Wed May 31 09:52:27 2006 Received: from sunmail2.sfbay.sun.com (sunmail2.SFBay.Sun.COM [129.149.246.180]) by sac.sfbay.sun.com (8.13.6+Sun/8.13.6) with ESMTP id k4VGqRrO009683 for ; Wed, 31 May 2006 09:52:27 -0700 (PDT) Received: from nwk-avmta-1.SFBay.Sun.COM (nwk-avmta-1.SFBay.Sun.COM [129.149.246.28]) by sunmail2.sfbay.sun.com (8.11.7p1+Sun/8.11.7/ENSMAIL,v2.2) with ESMTP id k4VGqR823124; Wed, 31 May 2006 09:52:27 -0700 (PDT) Received: from pmxchannel-daemon.nwk-avmta-1.sfbay.Sun.COM by nwk-avmta-1.sfbay.Sun.COM (Sun Java System Messaging Server 6.2 (built Dec 2 2004)) id <0J0500D052VCC800@nwk-avmta-1.sfbay.Sun.COM>; Wed, 31 May 2006 09:52:24 -0700 (PDT) Received: from nwkea-pix-1.sun.com ([10.4.134.6]) by nwk-avmta-1.sfbay.Sun.COM (Sun Java System Messaging Server 6.2 (built Dec 2 2004)) with ESMTP id <0J0500D2N2VC9P00@nwk-avmta-1.sfbay.Sun.COM>; Wed, 31 May 2006 09:52:24 -0700 (PDT) Received: from d1-sfbay-02.sun.com ([192.18.39.112]) by nwkea-pix-1.sun.com (8.12.10+Sun/8.12.9) with ESMTP id k4VGqN73003727; Wed, 31 May 2006 09:52:23 -0700 (PDT) Received: from conversion-daemon.d1-sfbay-02.sun.com by d1-sfbay-02.sun.com (Sun Java System Messaging Server 6.2-4.02 (built Sep 9 2005)) id <0J0500M012U7C200@d1-sfbay-02.sun.com> (original mail from Sherri.Shieh@Sun.COM); Wed, 31 May 2006 09:52:23 -0700 (PDT) Received: from [129.146.11.205] by d1-sfbay-02.sun.com (Sun Java System Messaging Server 6.2-4.02 (built Sep 9 2005)) with ESMTPSA id <0J05008YH2V6RN30@d1-sfbay-02.sun.com>; Wed, 31 May 2006 09:52:23 -0700 (PDT) Date: Wed, 31 May 2006 09:52:18 -0700 From: Sherri Shieh Subject: PSARC fast track: 2006/303 ZFS Clone Promotion Sender: Sherri.Shieh@Sun.COM To: psarc@Sun.COM, Jeff Bonwick , Matthew Ahrens Message-id: <447DC9C2.6020803@Sun.COM> MIME-version: 1.0 Content-type: text/plain; format=flowed; charset=ISO-8859-1 Content-transfer-encoding: 7BIT X-Accept-Language: en-us, en X-PMX-Version: 5.2.0.264296 User-Agent: Mozilla/5.0 (X11; U; SunOS sun4u; en-US; rv:1.7) Gecko/20050530 Status: RO Content-Length: 358 The foolowing fast track was approved 2 weeks ago. I'm marking closed approved. - Sherri -- ========================================================= Sherri Shieh Sun Microsystems, Inc. Program Manager Email: sherri.shieh@sun.com Systems Architecture Phone: 650-786-5245/x85245 =========================================================== From sacadmin Mon Jul 17 16:25:27 2006 Received: from zion.eng.sun.com (zion.SFBay.Sun.COM [129.146.17.75]) by sac.sfbay.sun.com (8.13.6+Sun/8.13.6) with ESMTP id k6HNPRPd025876 for ; Mon, 17 Jul 2006 16:25:27 -0700 (PDT) Received: from cathy (cathy [129.146.228.63]) by zion.eng.sun.com (8.13.7+Sun/8.13.7) with SMTP id k6HNPQ8m019372 for ; Mon, 17 Jul 2006 16:25:26 -0700 (PDT) Message-Id: <200607172325.k6HNPQ8m019372@zion.eng.sun.com> Date: Mon, 17 Jul 2006 16:25:08 -0700 (PDT) From: Jeff Bonwick Reply-To: Jeff Bonwick Subject: PSARC/2006/303 (ZFS Clone Promotion) To: psarc@sac.sfbay.sun.com MIME-Version: 1.0 Content-Type: TEXT/plain; charset=us-ascii Content-MD5: ZW8ls0HlbquQixsC4ffXAw== X-Mailer: dtmail 1.3.0 @(#)CDE Version 1.7_34 SunOS 5.11 sun4u sparc Status: RO Content-Length: 79 Folks, Just for the record -- this case was for patch release binding. Jeff