Recently, I had to remove a directory containing 2.75 million files (some php debug blunder) in a vserver sub-directory of
a machine which already ran under heavy I/O load. None of
rm -r $dir
find $dir -exec rm {} \;
ls $dir | xargs rm
was an option, since each would hog I/O, and the delay for productive tasks was unacceptable. Buffer cache was not an issue,
plenty of memory being always available, and each large chain of multiple indirect blocks could be held in memory, processing
each return from getdents(2) as it was delivered. Not so with ls, find et al, since those were hogging memory too and invalidating parts of the file system buffer cache while reading all entries.
Using perl, a readdir() loop, select() and unlink() solved that. My point is that readdir() gives you finer control than shelling out ls.
-
Are you posting in the right place? Check out Where do I post X? to know for sure.
-
Posts may use any of the Perl Monks Approved HTML tags. Currently these include the following:
<code> <a> <b> <big>
<blockquote> <br /> <dd>
<dl> <dt> <em> <font>
<h1> <h2> <h3> <h4>
<h5> <h6> <hr /> <i>
<li> <nbsp> <ol> <p>
<small> <strike> <strong>
<sub> <sup> <table>
<td> <th> <tr> <tt>
<u> <ul>
-
Snippets of code should be wrapped in
<code> tags not
<pre> tags. In fact, <pre>
tags should generally be avoided. If they must
be used, extreme care should be
taken to ensure that their contents do not
have long lines (<70 chars), in order to prevent
horizontal scrolling (and possible janitor
intervention).
-
Want more info? How to link
or How to display code and escape characters
are good places to start.
|