General discussion

Locked

Prob w/ NT40 server, deleting huge files

By time traveller ·
I have Dell Poweredge 4300 server, NT40 with a PERC II, 4 channel Raid controller . 1 channel is the mirrored system drive, and the other 2 channels are RAID 5, 118 Gig and 350 Gig respectively.
I have a user who creates files as large as 4 gigabytes on the 350 Gig array when he runs a simulation program. There are also any number of files from 1KB up to 4 gigs created in the same folder. The last run he did created 200,000 files in one folder, with a total size of 10 Gigs.
When we try to delete these files to clean up, the CPU goes to 100% and all other users are effectively locked out for about 10 minutes until the process is complete.
What causes this? How can we delete these huge files w/out bringing the system to a halt. We have tried moving them (the huge ones) to another folder, but the problem persisists. Currently we have them scheduled to delete 20 or so at a time to minimize customer impact.
Is this a limitation of NTFS?

This conversation is currently closed to new comments.

6 total posts (Page 1 of 1)  
| Thread display: Collapse - | Expand +

All Comments

Collapse -

Prob w/ NT40 server, deleting huge files

by MtnSqs In reply to Prob w/ NT40 server, dele ...

When you delete it is making a copy to the recycle bin! This is probably a space problem.

Try running a DOS box and do the delete from there - that way there is no copy/backup.

If that works, then write a batch job that doe sthe delete with the switch on to prevent the copy to recycle bin - I can;t remember the switch setting but you'll find it in the help.

Collapse -

Prob w/ NT40 server, deleting huge files

by time traveller In reply to Prob w/ NT40 server, dele ...

been there, done that, still have the problem

Collapse -

Prob w/ NT40 server, deleting huge files

by Shanghai Sam In reply to Prob w/ NT40 server, dele ...

Poster rated this answer

Collapse -

Prob w/ NT40 server, deleting huge files

by Some Guy in Seattle In reply to Prob w/ NT40 server, dele ...

Risking a reject because this is not the answer you want to hear...

You are pretty much out of luck dealing with this scenario. Even adding RAM and upping the CPU speed won't help. The reason is the physical time it takes for the drive head to float back and forth across the platters upating each one of the clusters as to whether or not it is allowed to be written over. (side note: a deleted file is *not* deleted - the system just flags that cluster as being available for being written on- in the case of sending something to the recycle bin the OS just changes the directory pointer and marks it as available for deletion if the deletion parameters are met, as in "delete when disk is a 10% free space" or whatever.) With such a large amount of files taking up such a large amount of space, the CPU will peg out updating the pointers on all these files. Moving them to another folder is the same thing - the system has to still change the pointers to reference it to the new directory. The file itself is not physically moved (unless it's to a drive letter hosted on a different physical drive, but still same problem with network saturation added in).

Probably the only way to deal with it is to get this user to do his disk maintenance when no one else is using the system.

Again, apologies for not giving the answer you would like to hear.

Collapse -

Prob w/ NT40 server, deleting huge files

by time traveller In reply to Prob w/ NT40 server, dele ...

Poster rated this answer

Collapse -

Prob w/ NT40 server, deleting huge files

by time traveller In reply to Prob w/ NT40 server, dele ...

This question was closed by the author

Back to Desktop Forum
6 total posts (Page 1 of 1)  

Related Discussions

Related Forums