The output options of btrfs sub list seem a bit... arbitrary?
awkward? unhelpful?
Here's my problem: Given a path at some arbitrary point into a
mounted btrfs (sub)volume, find all subvolumes visible under that
point, and identify their absolute path names.
My test btrfs filesystem looks
gt;>>>> missing the obvious, though.
>>>>>>
>>>>>> If I do:
>>>>>>
>>>>>> btrfs sub create A btrfs sub create A/B btrfs sub snap A
>>>>>> A/B/C
>>>>>>
>>>>>> A,
gt;
>>>>> btrfs sub create A btrfs sub create A/B btrfs sub snap A
>>>>> A/B/C
>>>>>
>>>>> A, A/B, A/B/C have their top-level being 5. How would I get a
>>>>> new snapshot to be a child of A/B for instance?
>>>>&g
t;>
>>>> A, A/B, A/B/C have their top-level being 5. How would I get a
>>>> new snapshot to be a child of A/B for instance?
>>>>
>>>> In my case, 285, was not appearing in the btrfs sub list
>>>> output, 287 was a child of 285 with path &qu
gt; obvious, though.
>> >
>> > If I do:
>> >
>> > btrfs sub create A btrfs sub create A/B btrfs sub snap A A/B/C
>> >
>> > A, A/B, A/B/C have their top-level being 5. How would I get a new
>> > snapshot to be a child of A/B for instance?
&
e A btrfs sub create A/B btrfs sub snap A A/B/C
> >
> > A, A/B, A/B/C have their top-level being 5. How would I get a new
> > snapshot to be a child of A/B for instance?
> >
> > In my case, 285, was not appearing in the btrfs sub list output,
> > 287 was a chil
ugh.
>
> If I do:
>
> btrfs sub create A btrfs sub create A/B btrfs sub snap A A/B/C
>
> A, A/B, A/B/C have their top-level being 5. How would I get a new
> snapshot to be a child of A/B for instance?
>
> In my case, 285, was not appearing in the btrfs sub list output,
>
> If I do:
>
> btrfs sub create A
> btrfs sub create A/B
> btrfs sub snap A A/B/C
>
> A, A/B, A/B/C have their top-level being 5. How would I get a
> new snapshot to be a child of A/B for instance?
Hm. OK, that's not doing what I thought it was, then. I'l
that. What I don't get is how one
creates a subvol with a top-level other than 5. I might be
missing the obvious, though.
If I do:
btrfs sub create A
btrfs sub create A/B
btrfs sub snap A A/B/C
A, A/B, A/B/C have their top-level being 5. How would I get a
new snapshot to be a child of A/B
On Fri, May 27, 2011 at 12:06:44PM +0200, Andreas Philipp wrote:
>
> -BEGIN PGP SIGNED MESSAGE-
> Hash: SHA1
>
> On 27.05.2011 11:45, Hugo Mills wrote:
> > On Fri, May 27, 2011 at 10:30:29AM +0100, Stephane Chazelas wrote:
> >> 2011-05-27 10:12:24 +0100, Hugo Mills:
> >> [skipped useful
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
On 27.05.2011 11:45, Hugo Mills wrote:
> On Fri, May 27, 2011 at 10:30:29AM +0100, Stephane Chazelas wrote:
>> 2011-05-27 10:12:24 +0100, Hugo Mills:
>> [skipped useful clarification]
>>>
>>> That's all rather dense, and probably too much information
On Fri, May 27, 2011 at 10:30:29AM +0100, Stephane Chazelas wrote:
> 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 i
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 da
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
On 27.05.2011 11:12, Hugo Mills wrote:
> On Fri, May 27, 2011 at 09:47:33AM +0100, Stephane Chazelas wrote:
>> 2011-05-27 10:21:03 +0200, Andreas Philipp:
>> [...]
What do those top-level IDs mean by the way?
>>> The top-level ID associated with
On Fri, May 27, 2011 at 09:47:33AM +0100, Stephane Chazelas wrote:
> 2011-05-27 10:21:03 +0200, Andreas Philipp:
> [...]
> > > What do those top-level IDs mean by the way?
> > The top-level ID associated with a subvolume is NOT the ID of this
> > particular subvolume but of the subvolume containing
Is there a way to derive the subvolume ID from the stat(2)
st_dev, by the way.
# btrfs sub list .
ID 256 top level 5 path a
ID 257 top level 5 path b
# zstat +dev . a b
. 27
a 28
b 29
Are the dev numbers allocated in the same order as the
subvolids? Would there be any /sys, /proc, ioctl interface
2011-05-27 10:21:03 +0200, Andreas Philipp:
[...]
> > What do those top-level IDs mean by the way?
> The top-level ID associated with a subvolume is NOT the ID of this
> particular subvolume but of the subvolume containing it. Since the
> "root/initial" (sub-)volume has always ID 0, the subvolumes
On 27.05.2011 10:01, Stephane Chazelas wrote:
> 2011-05-26 22:22:03 +0100, Stephane Chazelas: [...]
>> I get a btrfs sub list output that I don't understand:
>>
>> # btrfs sub list /backup/ ID 257 top level 5 path
>> u1/linux/lvm+btrfs/storage/data/data ID 260
2011-05-26 22:22:03 +0100, Stephane Chazelas:
[...]
> I get a btrfs sub list output that I don't understand:
>
> # btrfs sub list /backup/
> ID 257 top level 5 path u1/linux/lvm+btrfs/storage/data/data
> ID 260 top level 5 path u2/linux/lvm/linux/var/data
> ID 262 top le
Hiya,
I get a btrfs sub list output that I don't understand:
# btrfs sub list /backup/
ID 257 top level 5 path u1/linux/lvm+btrfs/storage/data/data
ID 260 top level 5 path u2/linux/lvm/linux/var/data
ID 262 top level 5 path u1/linux/lvm+btrfs/storage/data/snapshots/2010-10-11
ID 263 top le
20 matches
Mail list logo
