Samba cannot write files over 4KB

I'm desperately trying to get decent file sharing between my Sam440 (OS4.1) and my Windows XP Pro SP3 box, before I can seriously use OS4.1, and things are not going very well:

Writing files from the Amiga to Windows box using SMBFS is incredibly slow (reading is fine), so I am trying Samba v2.2.5 instead. My Windows box can *read* files fine from the Amiga using Samba, however...

Windows is unable to *write* files to the Amiga, if they are 4096 bytes or larger! In those cases Windows reports "The request could not be performed because an I/O device error. (1117)". Checking the Samba logs, I see something like this:

Quote:

I have tried fiddling with all the smb.conf settings I could find (especially using the 'secret' web interface that runs on port 901 of the Amiga), but nothing seems to make any difference. I have also tried different filing systems (SFS/00, SFS/02 & FFS) without luck. Can anyone suggest anything?

@ChrisH

sorry I can't tell you anything but have you looked through this webpage?

http://www.birrabrothers.com/tiger/data/samba/

good luck

@Slayer
No, I followed Mikey_C's Idiots Guide. edit: It does not seem to contain anything helpful

@ChrisH

I'll try and re-install samba today, see how it goes and i'll see if I have the same problem as you.

@ChrisH

sorry about that, it was pointed out on EAB I believe that many people found the resources on that page invaluable guess it was a specific thing...

all hope rests on Mikey_Cs shoulders now? :D

@Slayer
No, thank you for the suggestion. If anyone else has any ideas, please make them.

@ChrisH

It's not a DMA issue is it? I suppose you'd probably see it in other areas too if it were, but maybe try disabling DMA on your drives and see if that helps - SAMBA is gonna put pressure on the network and the drive at exactly the same time, so it would be the best conditions for getting DMA errors...

@Daedalus
Copying to the RAM disk using Samba has the same problem, and the RAM disk should not have DMA issues just because the harddisk has DMA enabled.

@ChrisH

Hmmm... Try lowering your MTU, maybe the network is corrupting something because SMB is sending packets that are too big. I con't remember exactly where the setting is, but there's a Microsoft KnowledgeBase article about it. It involves editing your registry anyway. Your router (if you're using one) should also have this setting somewhere in the advanced settings. IIRC Samba has this setting in its config file, and it may be accessible through the SWAT system, but failing that, Roadshow should have the setting somewhere too. I've solved a lot of problems with networks by lowering this value - some of which involved shared drives, file transfers over a certain size etc. Using a value of 1400 should be safe and not degrade performance noticeably.

@Daedalus
Tried changing Windows MTU with a registry hack (I assume it worked), but it didn't help Samba. I can't see any MTU setting for Roadshow. Not yet tried MTU setting on router.

@ChrisH

I gave samba a go, unfortunately, my PC hard drive just died :(

@ChrisH

For Roadshow, it's in Devs:Netinterfaces/<yourinterface>
set it like
mtu=xxx

I tried changing Roadshow's MTU (thanks Elwood) and my Router's MTU, but neither helped, even after reboots.

Would be interested to know if anyone else can (or can't) write files (>4KB) to Samba on OS4.1 from Windows XP with Service Pack 3 (SP3).

@ChrisH

From Amiga to PC, I use Smbclient:
smbclient //mypc/share mypassword -U myuser

the user is created on the PC.

I used this to copy many files from the Amiga to the PC (even 700 MB files).

@ChrisH

I have absolutely no problems copying files between my PC and Amiga using the PC.

However using the Amiga to copy files sometimes works and sometimes fails.

What is even more annoying is failures do not always cause an error but the file has only been partially copied.

If I do get an error it is Object In Use. Eh???

This can occur after transferring 4k or 300M.

I get the same results with Vista, XP, OS4 and OS4.1.

The only workaround for me is to move files using the PCs.

@madmonkey
Sounds like you are using AsyncWB. Remove it from the WbStartup folder, then reboot, and you should now be able to copy files using Workbench reliably.

@ChrisH

Thx for that but removing AsyncWb makes no difference. It was looking promising but after successfully copying 1.3G of a 1.4G file, the copy failed with object in use

NB I'm using DirectoryOpus to move the files as Workbench hangs navigating folders on the PC.

@madmonkey
Ah, I should have said that ASyncWB only causes problems for Workbench file operations. Note that "AutoUpdateWB" may also cause problems with WB.

Perhaps I also have the same problem as you, but I would not know because the write speed has prevented me from testing SMBFS heavily.

@ChrisH

For me, I think the problem is with smbfs not samba or the network because transfers using the pc work correctly