bug#55724: cp --reflink=always failing when --reflink=auto reflinks successfully on OpenZFS

2022-05-31 Thread Rich
On Mon, May 30, 2022 at 7:31 PM Paul Eggert wrote: > On 5/30/22 08:04, Pádraig Brady wrote: > > Really the kernel has to behave appropriately there > > and not do the blanket assumption with EXDEV. > > I agree. VFS should be willing to try a cross-filesystem FICLONE. Not > only does copy_file_ran

bug#55724: cp --reflink=always failing when --reflink=auto reflinks successfully on OpenZFS

2022-05-30 Thread Paul Eggert
On 5/30/22 08:04, Pádraig Brady wrote: Really the kernel has to behave appropriately there and not do the blanket assumption with EXDEV. I agree. VFS should be willing to try a cross-filesystem FICLONE. Not only does copy_file_range not guarantee cloning; it is less efficient even when it doe

bug#55724: cp --reflink=always failing when --reflink=auto reflinks successfully on OpenZFS

2022-05-30 Thread Pádraig Brady
On 30/05/2022 10:13, Rich wrote: Hi! So, OpenZFS is adding reflink support Soon(tm), including across filesystems on a pool, which is nice. Unfortunately, Linux's VFS returns EXDEV for trying FICLONE or FICLONERANGE (but not copy_file_range) cross-filesystem before you ever ask the filesystem-s

bug#55724: cp --reflink=always failing when --reflink=auto reflinks successfully on OpenZFS

2022-05-30 Thread Rich
Hi! So, OpenZFS is adding reflink support Soon(tm), including across filesystems on a pool, which is nice. Unfortunately, Linux's VFS returns EXDEV for trying FICLONE or FICLONERANGE (but not copy_file_range) cross-filesystem before you ever ask the filesystem-specific code, so currently, the fol