From mboxrd@z Thu Jan  1 00:00:00 1970
From: Stephane Chazelas <stephane_chazelas@yahoo.fr>
Subject: Re: strange btrfs sub list output
Date: Fri, 27 May 2011 10:30:29 +0100
Message-ID: <chaz20110527093029.GA30613@seebyte.com>
References: <20110526212203.GA4611@yahoo.fr> <chaz20110527080157.GA27537@seebyte.com> <4DDF5EEF.6060706@gmail.com> <chaz20110527084733.GC27537@seebyte.com> <20110527091224.GA15627@carfax.org.uk>
Mime-Version: 1.0
Content-Type: text/plain; charset=us-ascii
To: Hugo Mills <hugo@carfax.org.uk>,
	Andreas Philipp <philipp.andreas@gmail.com>,
	linux-btrfs <linux-btrfs@vger.kernel.org>
Return-path: <linux-btrfs-owner@vger.kernel.org>
In-Reply-To: <20110527091224.GA15627@carfax.org.uk>
List-ID: <linux-btrfs.vger.kernel.org>

2011-05-27 10:12:24 +0100, Hugo Mills:
[skipped useful clarification]
> 
>    That's all rather dense, and probably too much information. Hope
> it's helpful, though.
[...]

It is, thanks.

How would one end up in a situation where the output of "btrfs
sub list ." has:

ID 287 top level 285 path data

How could a "subvolume 285" become a "top level"?

How does one get a subvolume with a top-level other than "5"?

-- 
Stephane