On Thu, Jul 09, 2015 at 08:48:00AM -0400, Austin S Hemmelgarn wrote: > On 2015-07-09 08:41, Sander wrote: > > 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". > > > No, there is a bit in the subvolume metadata that says whether it's > considered a snapshot or not.
Technically it's not really a bit. The snapshot relation is determined by the parent uuid value of a subvolume. > Internally, they are handled identically, > but it does come into play when you consider things like btrfs subvolume > show -s (which only lists snapshots), That was probably 'btrfs subvol list -s', though the 'subvol show' command prints all snapshots of a given subvolume. > which in turn means that certain > tasks are more difficult to script robustly. I don't deny the interface/output is imperfect for scripting purposes, maybe we can provide filters that would satisfy your usecase. -- To unsubscribe from this list: send the line "unsubscribe linux-btrfs" in the body of a message to majord...@vger.kernel.org More majordomo info at http://vger.kernel.org/majordomo-info.html
