15.10.2016 01:58, Alberto Bursi пишет:
>
>
> On 10/15/2016 12:17 AM, Chris Murphy wrote:
>> It should be -e can accept a listing of all the subvolumes you want to
>> send at once. And possibly an -r flag, if it existed, could
>> automatically populate -e. But the last time I tested -e I just got
>> errors.
>>
>> https://bugzilla.kernel.org/show_bug.cgi?id=111221
>>
>>
>
> Not a problem (for me anyway), I can send all subvolumes already with my
> script (one after another, but still automatically).
>
> What I can't do with btrfs commands is to send over the contents of a ro
> snapshot of / called for example "oldRootSnapshot", directly to
> "/tmp/newroot" (which is where I have mounted the other drive/volume).
>
Somehow this is expected - it sends one subvolume to another subvolume.
I am not sure whether zfs can do it either.
But speaking about openSUSE - it does not have any real data in `/' at
all - it is just skeleton of root filesystem with a couple of
directories where actual root is in one of /.snapshots subvolumes.
> The only thing I can do is send over the subvolume as a subvolume.
> So I end up with /tmp/newroot/oldRootSnapshot and inside oldRootSnapshot
> I get my root, not what I wanted.
>
> Only way I found so far is using rsync to move the contents of
> oldRootSnapshot in the /tmp/newroot by setting an exclusion list for all
> subvolumes, then run a deduplication with duperemove.
>
> So, is there something I missed to do that?
>
> -Alberto
> N�����r��y���b�X��ǧv�^�){.n�+����{�n�߲)���w* jg��� �����ݢj/���z�ޖ��2�ޙ���&�)ߡ�a���� �G���h��j:+v���w�٥
>
--
To unsubscribe from this list: send the line "unsubscribe linux-btrfs" in
the body of a message to [email protected]
More majordomo info at http://vger.kernel.org/majordomo-info.html
