Re: [PATCH v2] Btrfs-progs: avoid using btrfs internal subvolume path to send

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

 



Em 29-11-2013 16:37, Wang Shilong escreveu:
> From: Wang Shilong <wangsl.fnst@xxxxxxxxxxxxxx>
> 
> Steps to reproduce:
> 	# mkfs.btrfs -f /dev/sda
> 	# mount /dev/sda /mnt
> 	# btrfs subvolume create /mnt/foo
> 	# umount /mnt
> 	# mount -o subvol=foo /dev/sda /mnt
> 	# btrfs sub snapshot -r /mnt /mnt/snap
> 	# btrfs send /mnt/snap > /dev/null
> 
> We will fail to send '/mnt/snap',this is because btrfs send try to
> open '/mnt/snap' by btrfs internal subvolume path 'foo/snap' rather
> than relative path based on mounted point, this will return us 'no
> such file or directory',this is not right, fix it.

I was going to write to the list to report exactly this issue. In my
case, this happens when the default subvolume has been changed from id 5
to some other id. I get the error 'no such file or directory'. Currently
my workaround is to mount the root subvolume with -o subvolid=5 and then
do the send.

Also, I'd like to ask, are there plans to make the send and receive
commands resumeable somehow (or perhaps it is already, but couldn't see
how) ?

best,
Miguel Negrão



Attachment: signature.asc
Description: OpenPGP digital signature


[Index of Archives]     [Linux Filesystem Development]     [Linux NFS]     [Linux NILFS]     [Linux USB Devel]     [Linux Audio Users]     [Yosemite News]     [Linux Kernel]     [Linux SCSI]

  Powered by Linux