On Tue, May 31, 2011 at 2:32 PM, C Anthony Risinger wrote:
> On Tue, May 31, 2011 at 1:50 PM, Andreas Philipp
> wrote:
>>
>> -BEGIN PGP SIGNED MESSAGE-
>> Hash: SHA1
>>
>> On 31.05.2011 19:40, C Anthony Risinger wrote:
>>> On Tue, May 31, 2011 at 5:00 AM, Stephane Chazelas
>>> wrote:
>>>
On Tue, May 31, 2011 at 1:50 PM, Andreas Philipp
wrote:
>
> -BEGIN PGP SIGNED MESSAGE-
> Hash: SHA1
>
> On 31.05.2011 19:40, C Anthony Risinger wrote:
>> On Tue, May 31, 2011 at 5:00 AM, Stephane Chazelas
>> wrote:
>>> 2011-05-27 13:49:52 +0200, Andreas Philipp: [...]
> Thanks, I can
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
On 31.05.2011 19:40, C Anthony Risinger wrote:
> On Tue, May 31, 2011 at 5:00 AM, Stephane Chazelas
> wrote:
>> 2011-05-27 13:49:52 +0200, Andreas Philipp: [...]
Thanks, I can understand that. What I don't get is how one
creates a subvol w
On Tue, May 31, 2011 at 5:00 AM, Stephane Chazelas
wrote:
> 2011-05-27 13:49:52 +0200, Andreas Philipp:
> [...]
>> > Thanks, I can understand 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:
>> >
2011-05-27 13:49:52 +0200, Andreas Philipp:
[...]
> > Thanks, I can understand 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
>
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
On 27.05.2011 13:30, Stephane Chazelas wrote:
> 2011-05-27 10:45:23 +0100, Hugo Mills: [...]
>>> How could a "subvolume 285" become a "top level"?
>>
>>> How does one get a subvolume with a top-level other than "5"?
>>
>> This just means that subvolu
On Fri, May 27, 2011 at 12:30:10PM +0100, Stephane Chazelas wrote:
> 2011-05-27 10:45:23 +0100, Hugo Mills:
> [...]
> > > How could a "subvolume 285" become a "top level"?
> >
> > > How does one get a subvolume with a top-level other than "5"?
> >
> >This just means that subvolume 287 was cre
2011-05-27 10:45:23 +0100, Hugo Mills:
[...]
> > How could a "subvolume 285" become a "top level"?
>
> > How does one get a subvolume with a top-level other than "5"?
>
>This just means that subvolume 287 was created (somewhere) inside
> subvolume 285.
>
>Due to the way that the FS trees
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 top level 5 path
>> u2/linux/lvm/linux
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 level 5 path u1/linux/lvm+btr
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 level 5 p
19 matches
Mail list logo
