Opened 7 years ago

Closed 6 years ago

#166 closed defect (fixed)

Cannot delete file in a created directory on the OS/2 share

Reported by: dmik Owned by: diver
Priority: Feedback Pending Milestone: Samba Server for eCS (OS/2) 1.1.x
Component: Samba Server Version: Server 3.3.x
Keywords: Cc:


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.

Change History (8)

comment:1 Changed 7 years ago by dmik

Note that if the directory is first created locally on the server, and then a file is copied to that directory remotely by the samba client, this file can be deleted by the client w/o any problems.

My assumption is that when the OS/2 server creates a directory upon the remote client's request, it somehow screws up kLIBC permission bits for this directory which then will prevent it from performing the remote delete request.

comment:2 Changed 7 years ago by dmik

After torturing it with some more similar tests, the server has just failed.

comment:3 Changed 7 years ago by dmik

By failed I mean that the server stopped responding to client requests so I had to stop/start it.

comment:4 Changed 7 years ago by dmik

The same happens if I use both the Samba client (Linux, OS/2) and the Sharity client (Linux).

comment:5 Changed 7 years ago by dmik

Note that this problem does not exist in Samba 3.0.37-eCS 1.0.5-472.

comment:6 Changed 7 years ago by diver

  • Component changed from Unknown to Samba Server
  • Milestone set to Samba Server for eCS (OS/2) 1.1.0
  • Owner changed from nobody to diver
  • Priority changed from minor to Feedback Pending

also a log could help here

comment:7 Changed 7 years ago by herwigb

Just tried this szenario here using Server 1.1.0 (3.3.15) and Client 2.2.beta1 (3.5.11) and I CANNOT reproduce it - everything seems to work normally. We definitely need a logfile.

comment:8 Changed 6 years ago by dmik

  • Resolution set to fixed
  • Status changed from new to closed

With the latest samba 3.3 and my libc064 build which fixes the permission issue on HPFS386, I don't see any problems any longer.

Note: See TracTickets for help on using tickets.