Linux - ServerThis forum is for the discussion of Linux Software used in a server related context.
Welcome to LinuxQuestions.org, a friendly and active Linux Community.
You are currently viewing LQ as a guest. By joining our community you will have the ability to post topics, receive our newsletter, use the advanced search, subscribe to threads and access many other special features. Registration is quick, simple and absolutely free. Join our community today!
Note that registered members see fewer ads, and ContentLink is completely disabled once you log in.
If you have any problems with the registration process or your account login, please contact us. If you need to reset your password, click here.
Having a problem logging in? Please visit this page to clear all LQ-related cookies.
Introduction to Linux - A Hands on Guide
This guide was created as an overview of the Linux Operating System, geared toward new users as an exploration tour and getting started guide, with exercises at the end of each chapter.
For more advanced trainees it can be a desktop reference, and a collection of the base knowledge needed to proceed with system and network administration. This book contains many real life examples derived from the author's experience as a Linux system and network administrator, trainer and consultant. They hope these examples will help you to get a better understanding of the Linux system and that you feel encouraged to try out things on your own.
Click Here to receive this Complete Guide absolutely free.
The server I'm looking at had a directory with millions of file and almost 1GB space. This was due to a software bug and has been corrected since.
In order to delete the files, the host admin renamed the directory then ran a script to rm all files in it with sleep interval. It took about a month but the files have been deleted.
My problem is that the directory entry still shows the same 1GB disk space using ls -l.
I need to do a scan on the directory structure but commands like ls -R or grep -R get put in an uninterrupted disk sleep. I guess it comes from this huge directory (If you think the problem is different, please let me know).
What would be the best way to correct that directory entry or ideally delete it without crashing a quite busy production server to which I have no physical access ?
I've read somewhere that renaming it would work but I'd rather ask here first, make absolutely sure I don't crash it.
Linux version 2.6.18-194.11.4.el5PAE (firstname.lastname@example.org) (gcc version 4.1.2 20080704 (Red Hat 4.1.2-48)) #1 SMP Tue Sep 21 05:48:23 EDT 2010
Filesystem 1K-blocks Used Available Use% Mounted on
/dev/sda3 959228044 111934848 798567248 13% /