samba - Apr 2016 - Migration to vfs_fruit with existing AppleDouble files?

Hello!

I have a quite large installation that currently supports OSX clients by
forcing them to SMB1 with no streams (via the "nsmb.conf") file.

This setup forces the OSX clients to generate their own ._[FILENAME]
appledouble files for files with resource forks (like adobe documents).

We recently discovered the fine work that's been done on vfs_fruit and
wanted to see it it could help us.

We have setup a test bed with a newer version of samba and vfs_fruit
implemented and the behavior seems much better (faster, easier, etc) we
just have one issue we've found.

The OSX generated AppleDouble files are not compatible with the vfs_fruit
generated ones.

I think the difference (or at least part of it) is the files made by OSX
might have all streams in them not just the AFP_* streams and the files
themselves don't have xattr's set.

Ideally we would like to upgrade our existing server to a newer version
using vfs_fruit and letting the VFS handle the AppleDouble files.

Is there a way to support this?

Thanks!
-Scott

On Fri, Apr 22, 2016 at 03:18:31PM -0700, Scott Call
wrote:
> Hello!
> 
> I have a quite large installation that currently supports OSX clients by
> forcing them to SMB1 with no streams (via the "nsmb.conf") file.
> 
> This setup forces the OSX clients to generate their own ._[FILENAME]
> appledouble files for files with resource forks (like adobe documents).
> 
> We recently discovered the fine work that's been done on vfs_fruit and
> wanted to see it it could help us.
> 
> We have setup a test bed with a newer version of samba and vfs_fruit
> implemented and the behavior seems much better (faster, easier, etc) we
> just have one issue we've found.
> 
> The OSX generated AppleDouble files are not compatible with the vfs_fruit
> generated ones.
Compatible, but containing a different metadata subset. OS X generated
AppleDouble contain marshalled xattr, Samba's don't.
> I think the difference (or at least part of it) is the files made by OSX
> might have all streams in them not just the AFP_* streams and the files
> themselves don't have xattr's set.
Yes.
> Ideally we would like to upgrade our existing server to a newer version
> using vfs_fruit and letting the VFS handle the AppleDouble files.
vfs_fruit converts the AppleDouble files on access, the AppleDouble
marshalled xattrs are discareded however. It's not rocket science to
add code for migrating the xattr data, but it will probably take a few
days of tedious work.

Cheerio!
-slow

Thanks for the response!

This would be really helpful because we use a lot of old adobe type 1 fonts
that are 100% resource fork and are rendered unusable without the
marshalled xattr's in addition to the AFP_ streams.

While ideally having it seamlessly integrated into samba would be great, if
it's easier to run a one-time conversion utility we can do that too.

Thanks!
-S

On Wed, Apr 27, 2016 at 12:32 AM, Ralph Boehme <slow at samba.org> wrote:
> On Fri, Apr 22, 2016 at 03:18:31PM -0700, Scott Call wrote:
> > Hello!
> >
> > I have a quite large installation that currently supports OSX clients
by
> > forcing them to SMB1 with no streams (via the "nsmb.conf")
file.
> >
> > This setup forces the OSX clients to generate their own ._[FILENAME]
> > appledouble files for files with resource forks (like adobe
documents).
> >
> > We recently discovered the fine work that's been done on vfs_fruit
and
> > wanted to see it it could help us.
> >
> > We have setup a test bed with a newer version of samba and vfs_fruit
> > implemented and the behavior seems much better (faster, easier, etc)
we
> > just have one issue we've found.
> >
> > The OSX generated AppleDouble files are not compatible with the
vfs_fruit
> > generated ones.
>
> Compatible, but containing a different metadata subset. OS X generated
> AppleDouble contain marshalled xattr, Samba's don't.
>
> > I think the difference (or at least part of it) is the files made by
OSX
> > might have all streams in them not just the AFP_* streams and the
files
> > themselves don't have xattr's set.
>
> Yes.
>
> > Ideally we would like to upgrade our existing server to a newer
version
> > using vfs_fruit and letting the VFS handle the AppleDouble files.
>
> vfs_fruit converts the AppleDouble files on access, the AppleDouble
> marshalled xattrs are discareded however. It's not rocket science to
> add code for migrating the xattr data, but it will probably take a few
> days of tedious work.
>
> Cheerio!
> -slow
>