05.08.2016 02:32, Peter Holm пишет:
> 'btrfs subvolumee show' gives no path to btrfs system root (volid=5)
> when snapshot is in the folder of subvolume.
>
> Step to reproduce.
> 1.btrfs subvolume create xyz
> 2.btrfs subvolume snapshot xyz xyz/xyz
> 3.btrfs subvolume snapshot /xyz
This last
You are right. Typing error. Sorry.
Here is from my bash_history.
1 btrfs su create is-this-a-bug
*2 btrfs su snap is-this-a-bug is-this-a-bug
*3 btrfs su snap is-this-a-bug /mnt/btrfs/sdc16-svid-5/
*2.When snapshot is created with the same name as subvolume, then it
by default creates in the
I accidentally posted this to Andrei Borzenkov
I repost to the list with the first 3 lines added from what was earlier sent.
Regarding to my manual for btrfs-subvolume dated 01/19/2016 it says.
"If only is given, the subvolume will be named the basename of
. "
So 'btrfs su snap is a shortcut
06.08.2016 11:00, Peter Holm пишет:
> You are right. Typing error. Sorry.
> Here is from my bash_history.
>
> 1 btrfs su create is-this-a-bug
> *2 btrfs su snap is-this-a-bug is-this-a-bug
> *3 btrfs su snap is-this-a-bug /mnt/btrfs/sdc16-svid-5/
>
As I said, in my case it fails with "File
writing error.
replace "gives no path to" with "same path as"
/Peter Holm
2016-08-05 1:32 GMT+02:00, Peter Holm :
> 'btrfs subvolumee show' gives no path to btrfs system root (volid=5)
> when snapshot is in the folder of subvolume.
>
> Step to reproduce.
> 1.btrfs
'btrfs subvolumee show' gives no path to btrfs system root (volid=5)
when snapshot is in the folder of subvolume.
Step to reproduce.
1.btrfs subvolume create xyz
2.btrfs subvolume snapshot xyz xyz/xyz
3.btrfs subvolume snapshot /xyz
4.btrfs subvolumme show xyz
output
.
Snapshot(s)