[Samba] "stuck" new directories and Mac Finder hangs after upgrade to 4.2.11

[tackyy]

Implementing vfs_fruit appears to have fixed the issue. Thanks

One thing I noticed since I sent the message to the list is I had about a third of the smbd processes stuck as D. Watching ps obsessively yesterday after fruit was configured I noticed that that’s no longer the case.

Another thing I noticed is that this wasn’t an issue with new folders. This was an issue when people would upload or move multiple files at once. We had previously had a similar issue with earlier versions of Samba4… just not as acute, we wouldn’t get any D processes. People would just get kicked off. So it seems this was an issue we’d been having for a long time that just became a bigger deal when we went from 4.2.3 to 4.2.11.

My users are also reporting improved file browsing performance.

Cheers,
tack

> On Apr 27, 2016, at 12:38 AM, Ralph Boehme <slow at SAMBA.ORG> wrote:
> 
> On Tue, Apr 26, 2016 at 01:25:45PM -0700, tackyy wrote:
>> We’re a 99% Mac shop running El Capitan (10.11.4). We’d been running
>> Samba 4.2.3 on FreeBSD 10.0/ZFS for a while with minimal problems. I
>> recently upgraded to 4.2.11 because of Badlock. Now when users
>> create a new folder then try to move files into it the Finder hangs,
>> the user loses their connection to the server and if you try to ls
>> or rm those directories while shelled in those processes get stuck
>> as D+.
> 
> network trace and Samba level 10 log will tell you what's going on.
> 
>> There is no netatalk in our environment if that’s a factor. We don’t
>> have fruit, catia or streams_attr explicitly set in smb4.conf, nor
>> any of the fruit:* settings. Just zfsacl. Is this where I’m going
>> wrong? Would turning those on help?
> 
> It dramitcally changes the way the Mac uses the SMB connection, so it
> might get you rid of the issue.
> 
> Cheerio!
> -slow