lkml.org 
[lkml]   [1997]   [Nov]   [6]   [last100]   RSS Feed
Views: [wrap][no wrap]   [headers]  [forward] 
 
Messages in this thread
/
Date
From
SubjectRe: SMBFS & 2.1.62
Steve Clark wrote:
>
> I have ran into the following problem trying to use 2.1.62 and smbfs
> with both Win95 and WFW 3.11:
>
> If I copy a text file from my linux system to either of the above
> platforms and the target filename does not already exist, the file is
> copied but I receive and EIO error from the cp command. If I immediately
> try to do the same thing again I get the EIO error but now the length of
> the destination file is ZERO.
> This is cut from my log file
>
> Nov 5 14:58:07 pc-sec kernel: smb_newconn: server not locked, count=1
> Nov 5 14:58:07 pc-sec kernel: smb_offerconn: server not locked, count=1
>
> Nov 5 14:58:07 pc-sec kernel: smb_offerconn: state valid, pid=206
> Nov 5 15:03:18 pc-sec kernel: smb_errno: ERRDOS code 50, returning EIO
> Nov 5 15:08:28 pc-sec kernel: smb_errno: ERRDOS code 50, returning EIO
> Nov 5 15:16:31 pc-sec kernel: smb_newconn: server not locked, count=1
> Nov 5 15:16:31 pc-sec kernel: smb_offerconn: server not locked, count=1

Hi Steve,

I'm puzzled by your problem, as I haven't had any reports of problems of
this sort. The key seems to be the error code -- whenever smbfs
encounters an undocumented error code, it prints the log message and
maps it to EIO.

I'm beginning to wonder if there's something wrong with the way smbfs
picks up error codes -- perhaps a comparison with what Samba does is in
order.

If you want to try for a quick workaround, you could map the code 50 to
0 in smb_errno() (in the file fs/smbfs/proc.c) and see if that helps.

Regards,
Bill

\
 
 \ /
  Last update: 2005-03-22 13:40    [W:0.032 / U:39.336 seconds]
©2003-2020 Jasper Spaans|hosted at Digital Ocean and TransIP|Read the blog|Advertise on this site