Operating System - HP-UX
1824294 Members
5067 Online
109669 Solutions
New Discussion юеВ

Files not deleted from SAMBA share

 
Robert Thorneycroft
Valued Contributor

Files not deleted from SAMBA share

We are using Samba version 2.2.5 and sharing a LVM filesystem from an HP9000 running HPUX 11.00 (hostname tst01) to a win 2k server. We execute a script from the win2k server which copies all the files to another server and then deletes them from the share. Unfortunately, the command does not seem to delete all if the IDOC* files from the share. Does anyone know why this might be, and how to resolve it.

Thanks
Robert Thorneycroft
6 REPLIES 6
RAC_1
Honored Contributor

Re: Files not deleted from SAMBA share

Can you do dir \\tst01\edi\D11\our\IDOC* ??

Are the permissions are right for all IDOC* files? So that the user can delete them.
There is no substitute to HARDWORK
Robert Thorneycroft
Valued Contributor

Re: Files not deleted from SAMBA share

Hello Anil,

Yes you can cd to the directory, and all the files have the same permissions. Most of the IDOC* files get deleted by the command, but there always seem to be a few that get left behind.
RAC_1
Honored Contributor

Re: Files not deleted from SAMBA share

May be those files are being used by applications or programs.

If you have lsof(list open files utility) on unix box check if you have any files open. (All IDOC files), if some ar eopen note the files names and then try deleing the files as are doing.

You can also check open files with fuser command. fuser -fu IDOC*
There is no substitute to HARDWORK
RolandH
Honored Contributor

Re: Files not deleted from SAMBA share

You can see the locked files if you start "smbstatus" from your binary dir in your samba configuration.


Roland
Sometimes you lose and sometimes the others win
RAC_1
Honored Contributor

Re: Files not deleted from SAMBA share

also check smbstatus. May be files are locked.
There is no substitute to HARDWORK
Darren Prior
Honored Contributor

Re: Files not deleted from SAMBA share

Hi Robert,

A log level of 2 set in the [global] section of your smb.conf should provide enough info in the logs to identify what's going on here.

Out of interest, is there any pattern to the files that are left behind, in terms of their filenames or timestamps?

regards,

Darren.
Calm down. It's only ones and zeros...