[Bug 294010] NFSv4: cp fails when restoring from a ZFS snapshot (copy_file_range issue)
| Newsgroups | gmane.os.freebsd.devel.file-systems |
|---|---|
| Message-ID | <[email protected]/bugzilla/> |
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=294010 Rick Macklem <[email protected]> changed: What |Removed |Added ---------------------------------------------------------------------------- Assignee|[email protected] |[email protected] --- Comment #2 from Rick Macklem <[email protected]> --- Created attachment 269060 --> https://bugs.freebsd.org/bugzilla/attachment.cgi?id=269060&action=edit zfs_vnops_os.c: Add copy_file_range fallback for EROFS This patch adds EROFS to the list of error returns for zfs_clone_range() where zfs_copy_file_range() returns ENOSYS so that vn_generic_copy_file_range() will be used. zfs_clone_range() appears to check for a read-only file system for the output fs, but maybe ZFS doesn't recognize a snapshot as a separate file system from the output fs? Maybe the reporter can try this patch and see if it fixes the problem? -- You are receiving this mail because: You are the assignee for the bug.