[Samba] Input/Output error when saving to samba profile directory

[Dave Newman]

Well, I solved the problem. After using a network analyser, I found that the
Input/Output error was being caused by a STATUS_MEDIA_WRITE_PROTECTED, so I
knew it was definitely a permissions problem (annoying that it didn't expose
itself as a permissions error on the file system mount)

Knowing that the users could read and write to their profile directories
locally, then it definitely had to be in the way the profile directory was
being shared. I had assumed that in the absence of any other configuration,
then the linux permissions would hold, but Clearly I was wrong.

It was an incredibly simple change: I needed writable = yes in my profile
share, and this appears to have fixed the problem. Not sure why the default
smb.conf file didn't have this option for this share, but the amount of
hacking the file had had over the past few weeks, perhaps it was commented
out in the original.

In all, obviously  a newbie error. The main problem I had was that I
couldn't get anything to appear in the logs, and the error at the client
side was more akin to a network error than a filesystem permissions problem,
so I had real issues trying to zero in on the cause. Thankfully wireshark
pointed me in the direction to investigate.

Thanks for all of your help, and hopefully this message might appear on
people's searches in the future.

Bye for now!

On Mon, Mar 2, 2009 at 1:47 PM, Dave Newman <davey.newman at googlemail.com>wrote:

>
>> the profiles are stored on a different virtual disk, but I have mounted it
>> on /var/samba/profiles with full write access.
>>
>> If I log on to the linux machine with my user credentials, I can create
>> and delete files at the command line.
>> When I create an SMB mount as that user on a different linux machine, I
>> get an Input/Output Error if I try to change or delete a file.
>>
>>
>
> OK, I thought it might be a strange interaction with the virtual disk
> mount, so I simplified the situation by copying the profiles to the root
> partition. I still have the same problem (which is comforting in a way,
> because I have very little space on the root partition!)
>
> I think the next stage is to use a protocol analyser I suppose. Anyone got
> any suggestions?
>
> It's annoying as I've got lots of windows people asking me to put a windows
> domain server in, and if I can't get this working I suspect I'll have no
> choice :-(
>