[Samba] mount.cifs: regular freezes with s3fs

[Matthieu Patou]

On 10/18/2012 11:11 AM, steve wrote:
> On 18/10/12 19:52, Jeff Layton wrote:
>> On Thu, 18 Oct 2012 18:34:07 +0200
>> steve <steve at steve-ss.com> wrote:
>>
>>> On 18/10/12 18:28, John Drescher wrote:
>>>>> through user login, freeze (twice) and user logout until the login 
>>>>> prompt
>>>>> returned:
>>>>> https://dl.dropbox.com/u/45150875/cifs-freeze2
>>>>>
>>>>
>>>> When I click the above link I get:
>>>>
>>>> We can't find the page you're looking for. Check out our Help Center
>>>> and forums for help, or head back to home.
>>>>
>>>> John
>>>>
>>>
>>> Sorry, It hadn't synced. It's there now.
>>> Cheers,
>>> Steve
>>>
>>
>> In this one, I don't see any issues with oplock breaks. I also don't
>> see any calls that are taking longer than expected. I do see a bunch of
>> page-sized reads in the capture for what appear to be sequential reads.
>> Reads also seem to be serialized, which is makes me think its falling
>> into the readpage codepath.
>>
>> There were some fixes to rsize handling in later kernels, so it's
>> probably worthwhile to test those before you do too much debugging.
>>
>
> Hi
> I'm sure it's not a kernel issue:
>
> S4 DC, s3fs file server (s3fs on the DC), kernel 3.4.6 -> Freezes
> S4 DC, 3.6.3 file server, kernel 3.2.0 -> works fine
> S4 DC, 3.6.7 file server, kernel 3.4.6, -> works fine
>
> Summary: with a separate Samba 3 file server, the same kernel which 
> gives freezes under s3fs, works correctly.
Compare apple and apple, are you using the same configuration in 3.6.7 
than the one in s3fs (that is generated by Samba AD DC), most probably not.
Can you try two tracks:

1) try to make your samba 3.6.7 config looks like the one of s3fs, 
please note that some defaults have changed in s3fs like vfs_objects 
that force the use of acl_xattr, also you have to pay attention if there 
is folder/files in the share that you serve that are owned by 
users/group of the domain in both cases as you might in one case kick 
winbindd calls for each and every sid that you have and the other case 
you won't.

2) try to use a newer kernel with current s3fs to see if it resolves the 
problem.

Matthieu.


-- 
Matthieu Patou
Samba Team
http://samba.org