On Tue, 14 Dec 1999, Chris Kotacka wrote:
If I recall the original question and circumstances, this was not a filer on the verge of running into a major problem unless this guy got an answer fast... and I'm quite sure no mater how extensive the tree was/is that he was trying to remove would have been done by now using a normal rm -rf versus waiting for more than a day to get the "quickest" solution on the planet.
Sometimes people make problems more complicated than they need to be.
He wasn't trying to remove anything as I recall. He asked what was the fastest way to remove files as rm -rf over NFS seemed like a waste. I would venture to say that he did an rm -rf on a pretty dense tree and saw the wonderful performance and load on the filer. Then he asked the question.
I, myself, once populated a filer with a tree, if I recall correctly, 100 deep from the top and 100 wide at every level. I then did an rm -rf and watched the filer top out at 100% utilization for several minutes. Needless to say, rm -rf on a large tree is a VERY expensive operation.
Tom