From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: from www.humilis.net ([80.100.93.5]:59352 "EHLO panda.humilis.net" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1751803AbbGIMlY (ORCPT ); Thu, 9 Jul 2015 08:41:24 -0400 Date: Thu, 9 Jul 2015 14:41:21 +0200 From: Sander To: Austin S Hemmelgarn Cc: "Fajar A. Nugraha" , james harvey , linux-btrfs Subject: Re: btrfs subvolume clone or fork (btrfs-progs feature request) Message-ID: <20150709124121.GA25033@panda> Reply-To: sander@humilis.net References: <559E6411.6090109@gmail.com> MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii In-Reply-To: <559E6411.6090109@gmail.com> Sender: linux-btrfs-owner@vger.kernel.org List-ID: Austin S Hemmelgarn wrote (ao): > >What's wrong with "btrfs subvolume snapshot"? > > Well, personally I would say the fact that once something is tagged as > a snapshot, you can't change it to a regular subvolume without doing a > non-incremental send/receive. A snapshot is a subvolume. There is no such thing as "tagged as a snapshot". Sander