Bug 11673 - vfs_fruit problem when moving file between two ZFS filesystems within same share
vfs_fruit problem when moving file between two ZFS filesystems within same share
Status: NEW
Product: Samba 4.1 and newer
Classification: Unclassified
Component: VFS Modules
x64 Solaris
: P5 normal
: ---
Assigned To: Samba QA Contact
Samba QA Contact
Depends on:
  Show dependency treegraph
Reported: 2016-01-14 15:47 UTC by Thomas Werschlein
Modified: 2016-01-14 15:47 UTC (History)
0 users

See Also:


Note You need to log in before you can comment on or make changes to this bug.
Description Thomas Werschlein 2016-01-14 15:47:15 UTC
OS platform: Solaris 11.1
Filesystem: ZFS
Samba version: 4.3.4


Given this share configuration:

  writable = yes
  path = /rpool/myshare
  vfs objects = fruit streams_xattr

and the following filesystem layout:

# zfs list -r rpool/myshare
rpool/myshare      3.41G  55.1G    33K  /rpool/myshare
rpool/myshare/fs1  3.41G  55.1G  3.41G  /rpool/myshare/fs1
rpool/myshare/fs2    49K  55.1G    49K  /rpool/myshare/fs2

Note: fs1 and fs2 are ZFS filesystems, not directories.

When moving "myfile" from myshare/fs1 to myshare/fs2 on a Windows SMB client (Server 2012 R2 or Windows 10) by "drag & drop", the file "myfile" disappears at the source location, quickly pops up at the target location and disappears there, too.

In fact, nothing gets copied or moved, a refresh (F5) of the source directory window (myshare/fs1) makes "myfile" reappear.

When doing this with a whole directory structure, the directories get copied (not moved), but not the files within them. This makes it confusing, since you get the impression, that the move did actually work, while it did not.

Moving myshare/fs1/myfile to myshare/fs2/myfile by "drag & drop" with a share config like this (i.e. without vfs_fruit)

  writable = yes
  path = /rpool/myshare
  vfs objects = 

DOES work (performing a server-side move, which is actually a server-side copy & unlink since two filesystems are involved).

This leads me to the assumption that the combination of vfs_fruit and ZFS is the problem.