Marcel Mueller
2016-07-31 10:12:35 UTC
I need to connect to an OS/2 VM (eCS 1.05 with all patches, IBM Peer
Client) from a Linux box (Mint 17.3). (*1)
Up to now I used the built-in nfs 3 server of OS/2. But this very old
thing is buggy and when I switched from from svn to git it finally gave up.
Now the next idea was to use cifs. OK, I enabled LANMA2 authentication
on the client and adjusted the mount options (mainly servern= and
sec=lanman). Now I can mount the share, and access the files. But
unfortunately git hangs with errors during directory scan.
A Wireshark trace turned out that cifs uses an invalid TRANS2 info level
263 (Query File All Info). This info level did not exist in the LANMAN 2
protocol level. And so the server always responds with "Unknown Info Level".
Obviously cifs uses a higher protocol level than negotiated. This does
not only happen with to git. Other applications like Midnight Commander
or Eclipse raise the same errors. But they do not care that much about a
failed stat() calls.
Restricting "client max protocol" to LANMAN2 does not change anything.
Of course, this is a bug in cifs. But is there a Work around?
I cannot simply change the cifs module of Mint 17 (i.e. Ubuntu 14.04).
And if I could do so, is it fixed in newer Samba versions? I did not
find anything related in the Samba bug tracker.
Marcel
(*1) The development IDE resides on Linux but the files need to be
located on OS/2 because otherwise make and gcc take about 10 times
longer to compile. So I do not want to host the files on the Linux
machine and use the Samba shares from OS/2.
Client) from a Linux box (Mint 17.3). (*1)
Up to now I used the built-in nfs 3 server of OS/2. But this very old
thing is buggy and when I switched from from svn to git it finally gave up.
Now the next idea was to use cifs. OK, I enabled LANMA2 authentication
on the client and adjusted the mount options (mainly servern= and
sec=lanman). Now I can mount the share, and access the files. But
unfortunately git hangs with errors during directory scan.
A Wireshark trace turned out that cifs uses an invalid TRANS2 info level
263 (Query File All Info). This info level did not exist in the LANMAN 2
protocol level. And so the server always responds with "Unknown Info Level".
Obviously cifs uses a higher protocol level than negotiated. This does
not only happen with to git. Other applications like Midnight Commander
or Eclipse raise the same errors. But they do not care that much about a
failed stat() calls.
Restricting "client max protocol" to LANMAN2 does not change anything.
Of course, this is a bug in cifs. But is there a Work around?
I cannot simply change the cifs module of Mint 17 (i.e. Ubuntu 14.04).
And if I could do so, is it fixed in newer Samba versions? I did not
find anything related in the Samba bug tracker.
Marcel
(*1) The development IDE resides on Linux but the files need to be
located on OS/2 because otherwise make and gcc take about 10 times
longer to compile. So I do not want to host the files on the Linux
machine and use the Samba shares from OS/2.