[plug] Samba, delayed write failed, and can't become connected user

[sothisistheinternet]

Setting oplocks = no has also not helped. Here's my smb.conf:

# Samba config file created using SWAT
# from UNKNOWN (Æ)
# Date: 2009/04/05 07:33:50

[global]
	workgroup = MYLOCAL
	server string = FILES
	passdb backend = tdbsam
	username map = /etc/samba/smbusers
	log file = /var/log/samba/log.%m
	max log size = 50
	valid users = husband, wife, @family
	write list = husband, wife, @family
	create mask = 0660
	directory mask = 0770
	cups options = raw
	local master = yes
	os level = 255
	preferred master = yes
	wins support = yes
	name resolve order = wins lmhosts hosts bcast
	announce as = FC10
	oplocks = no

[printers]
	comment = All Printers
	path = /var/spool/samba
	printable = Yes
	browseable = No

[library]
	path = /pub/sambashare1/library
	read only = No

[music]
	path = /pub/sambashare1/music
	read only = No

[husbandbackup]
	path = /pub/sambashare3/aribackup
	read only = No

[camera]
	path = /pub/sambashare3/camera
	read only = No

[wifebackup]
	path = /pub/sambashare4/carobackup
	read only = No

[file-exchange]
	path = /pub/sambashare3/file-exchange
	read only = No

[lindownload]
	path = /pub/sambashare4/lindownload
	read only = No

[windownload]
	path = /pub/sambashare4/windownload
	read only = No

Any more ideas, guesses, random thoughts? :)

TIA,

Ari

On Tue, Apr 21, 2009 at 7:17 PM, sothisistheinternet
<sothisistheinternet at gmail.com> wrote:
> Thanks Daniel,
>
> I've done a bunch of trouble shooting and have been able to rule the
> switch out, but perhaps not the onboard NIC:
>
> I swapped in a different switch and cables - no effect
> I used the manufacturer's diagnostics and checked the filesystems on
> the drives - nothing wrong
> Restarting smb fixes the issue - until then, no computers can connect
> Problem began just after installing FC10 after having been using FC5 for ages
>
> Any other ideas would be very much appreciated. It's driving me nuts
> and causing problems with my downloads.
>
> Ari
>
> On Tue, Apr 21, 2009 at 6:34 PM, Daniel Foote <freefoote at gmail.com> wrote:
>> Hello.
>>
>>> Anyone? I made the FC10 system the master browser and thought that had
>>> corrected the problem, think the problem was being caused by
>>> elections. It was good for about 36 hours then during the night two
>>> more episodes of 'delayed write failed' during PTP file transfers,
>>> each require a sudo service smb restart to get samba to let other
>>> computers on the network access it again.
>>
>> The last time I saw something like this, it was caused by a gigabit
>> network card (windows client machine) on a 100mbit switch, connected
>> to a Linux server (samba) with a 100mbit network card. Something
>> related to the gigabit card, the cabling, or the switch caused it to
>> 'micro-dropout' (I estimate 10ms or less) - just long enough to
>> disconnect the Windows client from the samba server. In this case, it
>> caused this Windows machine to emit the 'delayed write failed'
>> message, and also released locks that the machine had on certain
>> shared files, causing other issues.
>>
>> Not sure if that will help in your case... but something to consider.
>>
>> Daniel Foote.
>> _______________________________________________
>> PLUG discussion list: plug at plug.org.au
>> http://www.plug.org.au/mailman/listinfo/plug
>> Committee e-mail: committee at plug.linux.org.au
>>
>