[plug] Samba, delayed write failed, and can't become connected user
sothisistheinternet at gmail.com
Thu Apr 23 07:59:31 WST 2009
On Wed, Apr 22, 2009 at 7:36 PM, sothisistheinternet
<sothisistheinternet at gmail.com> wrote:
> 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:
> Bought a PCI nic today. As of now, there's a new NIC and new CAT5
> cable and the samba server is connected directly to a router ethernet
> port, not the switch, as is the PC that's been having the most issues.
Happened again. Bug report time. I'm ruing this OS update :(
>> 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.
>> On Tue, Apr 21, 2009 at 6:34 PM, Daniel Foote <freefoote at gmail.com> wrote:
>>>> 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
>>> Committee e-mail: committee at plug.linux.org.au
More information about the plug