Custom Query (292 matches)

If you copy a bunch of files to the OS/2 share, some files will have their original dates, some files will get the current date.

To me, it looks like the time stamp is not always updated correctly on the server after the copy operation is completed.

Steps to reproduce:

1. Connect to an OS/2 share.
2. Copy a bunch of files from your local machine to it.
3. Compare the file timestamps with the originals.

If I create a directory through a Samba client on an OS/2 share and copy a file to that directory, I cannot delete this file through the client (it may be deleted only locally on the server).

Steps to reproduce:

1. Connect to an OS/2 share.
2. Create a directory.
3. Copy a file to that directory from the local machine or create it from scratch.
4. Attempt to delete this file. You will get the "Access denied" ("Permission denied") error.

I've just noticed that working with file on an OS/2 share from a remote client sometimes leaves these files in a locked state on the server so that they cannot be opened locally for writing or deleted, even though the file is closed by the remote client. It takes some time for this lock to go away (tens seconds to minutes).

Steps to reproduce:

1. Connect to an OS/2 share with the Sharity client.
2. Open some file (with e.g. an editor), then close it.
3. Attempt to open the file for writing locally on the server -- you will get "The process cannot access the file because it is being used by another process (32)". An attempt to delete it gives "Sharing violation".

Note that you can perfectly save to the same file from the remote client or even delete it from there.