There certainly appears to be a problem with the Hardy CIFS/SMBFS implementation. For me it has broken a wine application that used smbfs/cifs to access a remote set of files.
We use an old Windows based account packages (TAS Books). Works fine and runs under Linux/wine, so no real need to replace it. It uses a Btrieve database implemented as a set of files in the same directory. In our deployment, the database files are on a remote server with the directory mounted as a remote share. This allows access from several clients (but not simultaneous). The setup worked fine under ubuntu 7.10. Both server and clients were upgraded to Hardy last weekend and this broke the application. It claims that the remote files are being used by a "Maintenance Utility"- although other wine apps can open them for reading. The fstab entry seems pretty standard: //myserver/tasdata /home/tony/tasdata cifs credentials=/etc/samba/mysecret,uid=1000,gid=1000,auto,rw 0 0 Restarting a client with the 2.6.22 kernel (no other change) fixes the problem and the application works. So the problem (change) seems to be in the kernel or one of its loadable modules. The mounts appear to work, regardless of whether they are declared as cifs or smbs and the remote files are accessible through bash and text editors. All permissions appear correct - but something has changed - and that something breaks the application. As TAS Books is closed source, it's difficult to know what it is doing and why it can't see the files. My guess is that it can't get a file lock on one or more files - but that's just a guess. Alternatively, it may be something to do with opening a file for read/write. Tony -- no way to read and write files on mounted samba share on hardy https://bugs.launchpad.net/bugs/210741 You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
