samba - Nov 2002 - FYI : oplock problems

FYI, I'm setting up a file server for 1000 users based on mdk 8.0,
self-compiled 2.4.19 + acl patches, self compiled samba 2.2.6, 100 Mbps NIC

this server is right now in a pre-prod status and is currently used only by
very few users

while loading several +100 MB files on a share from a NT 4 wks 100 Mbps, we
got several "session cancelled" messages, and un-killable D-state smbd
processes on the server. 

setting "oplocks = no" on the share and rebooting (the only way to
remove
D-state processes in this case) solved the problem

oplocks are definitively a nightmire for us here...


			- * - * - * - * - * - * -
Bien s?r que je suis perfectionniste !
Mais ne pourrais-je pas l'?tre mieux ?
	Thierry ITTY
eMail : Thierry.Itty@Besancon.org		FRANCE

On Wed, Nov 20, 2002 at 09:36:18AM +0000, Thierry ITTY
wrote:
> FYI, I'm setting up a file server for 1000 users based on mdk 8.0,
> self-compiled 2.4.19 + acl patches, self compiled samba 2.2.6, 100 Mbps NIC
> 
> this server is right now in a pre-prod status and is currently used only by
> very few users
> 
> while loading several +100 MB files on a share from a NT 4 wks 100 Mbps, we
> got several "session cancelled" messages, and un-killable D-state
smbd
> processes on the server. 
This is a kernel bug. 'D' states are *always* kernel bugs.
> setting "oplocks = no" on the share and rebooting (the only way
to remove
> D-state processes in this case) solved the problem
> 
> oplocks are definitively a nightmire for us here...
You could have turned off kernel oplocks - looks like you have a problem
with this kernel.

Jeremy.