Stux
MVP
- Joined
- Jun 2, 2016
- Messages
- 4,419
So,
I'm trying to setup an SMB share so that Mac OS X users can use it. We have legacy content with resource forks exceeding 128KiB.
It is the sole share on the FreeNAS box.
I'm trying to rsync the legacy content from a Mac OS X Server to the share, but its not copying the resource forks on files greater than 128KiB.
I'm using Carbon Copy Cloner 4.1.10 (latest version) on the Mac OS X Server (10.9.5)
The problem is illustrated with these two log lines
oh-oh.
and
And yes, if I check the file on the share, it has a Resource Fork of 0 bytes, where it should be more like 150KB.
Now, I've added vfs_fruit to the cifs share "shared" already. Which is I believe supposed to fix this.
And I've also then begun trying to add various auxillary parameters, based on the vfs_fruit manpage
"fruit:resource file", although it is supposed to be the default, is supposed to work around this limitation in freebsd's zfs x_attr support.
Nothing seems to help.
Any ideas?
I'm trying to setup an SMB share so that Mac OS X users can use it. We have legacy content with resource forks exceeding 128KiB.
It is the sole share on the FreeNAS box.
I'm trying to rsync the legacy content from a Mac OS X Server to the share, but its not copying the resource forks on files greater than 128KiB.
I'm using Carbon Copy Cloner 4.1.10 (latest version) on the Mac OS X Server (10.9.5)
The problem is illustrated with these two log lines
2F0A4289| 09/28 14:47:51 DEBUG: Max xattr size for the destination filesystem is 131072 bytes
oh-oh.
and
2F0A4289| 09/28 14:47:51 The "com.apple.ResourceFork" extended attribute on "/Volumes/shared/<redacted>" is too large (151488 bytes) to be preserved on the destination.
And yes, if I check the file on the share, it has a Resource Fork of 0 bytes, where it should be more like 150KB.
Now, I've added vfs_fruit to the cifs share "shared" already. Which is I believe supposed to fix this.
And I've also then begun trying to add various auxillary parameters, based on the vfs_fruit manpage
"fruit:resource file", although it is supposed to be the default, is supposed to work around this limitation in freebsd's zfs x_attr support.
Nothing seems to help.
Any ideas?