I’ve got a problem with fs-cifs that it doesn’t seem to want to recognize a
file as a file. Programs that attempt to open the file get various i/o
errors. In diffing the verbose output of cifs from syslog, I can see that
for files it’s getting, it calls stat(), whereas for the file it’s not, it
seems to be calling smb_chkdir() and that seems to be the downfall. I’ve
appended output of syslog, with the host and file names changed to protect
the innocent.
We’ve rebooted the involved machines numerous times, and the symptoms are
the same for two different Patch B NTO boxes pointing to the same WinNT SP5
box.
Any hints in here?
Mar 19 17:45:03 nto fs-cifs: open( host:\FileThatDoesntWork )
Mar 19 17:45:03 nto fs-cifs: smb_stat2 (host:\FileThatDoesntWork)
Mar 19 17:45:03 nto fs-cifs: need to open for stat
Mar 19 17:45:03 nto fs-cifs: smb_open: host:\FileThatDoesntWork with mode 0,
uid 100
Mar 19 17:45:03 nto fs-cifs: returning: mid 1A status= 0
Mar 19 17:45:03 nto fs-cifs: host:\FileThatDoesntWork is not locked, and was
opened fid= 2048 srvfid =0
Mar 19 17:45:03 nto fs-cifs: smb_stat2 (host:\d:2048)
Mar 19 17:45:03 nto fs-cifs: returning: mid 1B status= 0
Mar 19 17:45:03 nto fs-cifs: smb_close: host:\d fid: 2048
Mar 19 17:45:03 nto fs-cifs: returning: mid 1C status= 0
Mar 19 17:45:03 nto fs-cifs: smb_chkdir: host:\FileThatDoesntWork
Mar 19 17:45:04 nto fs-cifs: returning: mid 1D status= 13
Mar 19 17:45:04 nto fs-cifs: smb_chkdir: Permission denied
Mar 19 17:45:04 nto fs-cifs: open( host:\FileThatDoesntWork ): Permission
denied
Mar 19 17:45:04 nto fs-cifs: open( host:\FileThatDoesntWork )
Mar 19 17:45:04 nto fs-cifs: smb_stat2 (host:\FileThatDoesntWork)
Mar 19 17:45:04 nto fs-cifs: need to open for stat
Mar 19 17:45:04 nto fs-cifs: smb_open: host:\FileThatDoesntWork with mode 0,
uid 100
Mar 19 17:45:04 nto fs-cifs: returning: mid 1E status= 0
Mar 19 17:45:04 nto fs-cifs: host:\FileThatDoesntWork is not locked, and was
opened fid= 2049 srvfid =0
Mar 19 17:45:04 nto fs-cifs: smb_stat2 (host:\d:2049)
Mar 19 17:45:04 nto fs-cifs: returning: mid 1F status= 0
Mar 19 17:45:04 nto fs-cifs: smb_close: host:\d fid: 2049
Mar 19 17:45:04 nto fs-cifs: returning: mid 20 status= 0
Mar 19 17:45:04 nto fs-cifs: smb_chkdir: host:\FileThatDoesntWork
Mar 19 17:45:04 nto fs-cifs: returning: mid 21 status= 13
Mar 19 17:45:04 nto fs-cifs: smb_chkdir: Permission denied
Mar 19 17:45:04 nto fs-cifs: open( host:\FileThatDoesntWork ): Permission
denied
Mar 19 17:47:26 nto fs-cifs: open( host:\FileThatDoesWork )
Mar 19 17:47:26 nto fs-cifs: smb_stat2 (host:\FileThatDoesWork)
Mar 19 17:47:26 nto fs-cifs: need to open for stat
Mar 19 17:47:26 nto fs-cifs: smb_open: host:\FileThatDoesWork with mode 0,
uid 100
Mar 19 17:47:26 nto fs-cifs: returning: mid 3A status= 0
Mar 19 17:47:26 nto fs-cifs: host:\FileThatDoesWork is not locked, and was
opened fid= 2050 srvfid =0
Mar 19 17:47:26 nto fs-cifs: smb_stat2 (host:\d:2050)
Mar 19 17:47:26 nto fs-cifs: returning: mid 3B status= 0
Mar 19 17:47:26 nto fs-cifs: smb_close: host:\d fid: 2050
Mar 19 17:47:26 nto fs-cifs: returning: mid 3C status= 0
Mar 19 17:47:26 nto fs-cifs: stat(host:\FileThatDoesWork)
Mar 19 17:47:26 nto fs-cifs: close( host:\FileThatDoesWork:-1 )
Mar 19 17:47:26 nto fs-cifs: open( host:\FileThatDoesWork )
Mar 19 17:47:26 nto fs-cifs: smb_stat2 (host:\FileThatDoesWork)
Mar 19 17:47:26 nto fs-cifs: need to open for stat
Mar 19 17:47:26 nto fs-cifs: smb_open: host:\FileThatDoesWork with mode 0,
uid 100
Mar 19 17:47:26 nto fs-cifs: returning: mid 3D status= 0
Mar 19 17:47:26 nto fs-cifs: host:\FileThatDoesWork is not locked, and was
opened fid= 2051 srvfid =0
Mar 19 17:47:26 nto fs-cifs: smb_stat2 (host:\d:2051)
Mar 19 17:47:26 nto fs-cifs: returning: mid 3E status= 0
Mar 19 17:47:26 nto fs-cifs: smb_close: host:\d fid: 2051
Mar 19 17:47:26 nto fs-cifs: returning: mid 3F status= 0
Mar 19 17:47:26 nto fs-cifs: smb_open: host:\FileThatDoesWork with mode 21,
uid 100
Mar 19 17:47:26 nto fs-cifs: returning: mid 40 status= 0
Mar 19 17:47:26 nto fs-cifs: host:\FileThatDoesWork is not locked, and was
opened fid= 2052 srvfid =0
Mar 19 17:47:26 nto fs-cifs: read( host:\FileThatDoesWork fid 2052 )
nbytes:765 off:0 blk 0 boff 0
Mar 19 17:47:26 nto fs-cifs: reading fid[2052] blk[0]
Mar 19 17:47:26 nto fs-cifs: smb_read: host:\d fid 2052 len 4096 off 0
Mar 19 17:47:26 nto fs-cifs: returning: mid 41 status= 0
Mar 19 17:47:26 nto fs-cifs: smb_read( 2052 ) read 765 bytes
Mar 19 17:47:26 nto fs-cifs: read EOF: fid[2052] last read: 765 bytes blk 0
Mar 19 17:47:26 nto fs-cifs: close( host:\FileThatDoesWork:2052 )
Mar 19 17:47:26 nto fs-cifs: smb_close: host:\d fid: 2052
Mar 19 17:47:26 nto fs-cifs: returning: mid 42 status= 0
\
“Patrick Mueller” <Patrick_Mueller@oti.com> wrote in message
news:9963ht$195$1@nntp.qnx.com…
I’ve got a problem with fs-cifs that it doesn’t seem to want to recognize
a
file as a file. Programs that attempt to open the file get various i/o
errors.
I am seeing a similar (the same?) problem. I have a Win2K server box from
which my QNX boxes mount a ‘/public’ area using ‘fs-cifs’ and an allocated
account on the NT box (‘qnx’):
/usr/sbin/fs-cifs -a //Server:server:/Public /public qnx password &
This has worked fine up to now but with patch B I am getting weird file
permission errors - e.g. sometimes I can create and edit a file but not open
it later nor open any files created before the upgrade which are already on
the disk. The NT permissions are ok (full access for ‘Everybody’).
James
I’ve taken an fs-cifs executable from a patchA system, put it on my patchB
system, and my problem has gone away.
Complete guess, but given that I only appeared to have a problem with one
file, and it seemed to think it was a directory, I’m thinking maybe fs-cifs
hashes entries for a cache, and I was encountering a hash conflict between
the file and some other directory. There was nothing different about that
file compared to any of the others I could access, besides the name
(obviously), file contents (obviously, but I suspect it appears to not have
gotten to the point of looking that far), and nothing different about it on
the NT system …
I checked to see if fs-cifs was on cvs yet, but cvs is still pretty sparse
…
–