Hi Govind,
That shouldn't happen, unless rfrm was unable to delete the file in
question. Can you check if the file actually does exist, and what
storage node it's on (and if it really does exist on that storage
node)?
Sam
On 3 February 2011 14:17, Govind Songara <[log in to unmask]> wrote:
> Wahid,
>
> When i try to delete it complains about files exist.
> [root@se2 ~]# rfrm -rf /dpm/ppgrid1.rhul.ac.uk/home/atlas/atlasmcdisk/
> rmdir(/dpm/ppgrid1.rhul.ac.uk/home/atlas/atlasmcdisk//mc10_7TeV/AOD/e600_s933_s946_r1831_r1700/mc10_7TeV.107660.AlpgenJimmyZmumuNp0_pt20.merge.AOD.e600_s933_s946_r1831_r1700_tid219397_00):
> File exists
>
> How to deal the exist files.
>
> Thanks
> Govind
>
>
> On Thu, Feb 3, 2011 at 11:55 AM, Wahid Bhimji <[log in to unmask]>
> wrote:
>>
>> Alessandra,
>>
>> You can use
>>
>> rfrm -rf
>>
>> and that is better as it also deletes the physical files whereas dpns-rm
>> will only delete the database entries.
>> It can take a while though (dpns-rm is quicker if you know the physical
>> files are not there (and actually I thought it also took an -rf which will
>> delete all sub-dirs and files))
>>
>> Cheers
>>
>> Wahid
>>
>> On 3 Feb 2011, at 11:51, Alessandra Forti wrote:
>>
>> > Hi,
>> >
>> > I don't know if there is any receipe to delete DPM dirs quickly I
>> > couldn't find any script. This is the quickest way I could come up with.
>> >
>> > for dir in `cat dir-list`; do
>> >
>> > for a in `dpns-rm -r $dir 2>&1 | grep File|cut -f1 -d':'`; do
>> >
>> > echo "Deleting $a";
>> > rfrm $a
>> >
>> > done
>> >
>> > dpns-rm -r $dir
>> >
>> > done
>> >
>> > the first dpns-rm all the subdirs that are already empty, the second
>> > cleans the leftovers after the files have been deleted.
>> >
>> > If there is a better way let me know.
>> >
>> > cheers
>> > alessandra
>> >
>>
>>
>> --
>> The University of Edinburgh is a charitable body, registered in
>> Scotland, with registration number SC005336.
>>
>> __________ Information from ESET NOD32 Antivirus, version of virus
>> signature database 5842 (20110203) __________
>>
>> The message was checked by ESET NOD32 Antivirus.
>>
>> http://www.eset.com
>>
>>
>>
>
>
|