The easiest way to test your NICs is to bypass any other network equipment you have and connect two of your machines with a null aka crossover cable. Then transfer a few large files back and forth and verify them with MD5s (which you generated beforehand).

Running your HDD over 90% capacity is sure to bog your system down due to extreme fragmentation and virtual memory problems. To list by file size, try "ls PATH -R -S -l" where PATH is the directory from which you want to start searching. (You could also use find, but no matter.)

Also, if you don't have the HDD partitioned yet, do so sometime and place the data you're serving up on one of the other partitions. Then, when it gets full again, it won't affect your system so badly. This trick even works in Windoze - even "Program Files" lives on D: so that I can leave at least a Gig for M$ to put DLLs, drivers, etc on. Call it OT, but it just support my point.

Good luck! :c)

Shawn Grover wrote:

One of the server's I have inherited in the past week has suddenly decided
to stop serving it's web pages and/or has encountered a problem with a
network card.

My guess thus far is that we either have run out of drive space, or our NICs
aren't comming up right when the system boots.

So, first, I'm looking for an appropriate command to find the largest files
on the drive (I'll be checking google after I send this message, but our
primary site is down - kinda urgent to get this fixed). Any tips?





Reply via email to