I was watching LimeWire's disk activity while it's calculating bitrates of MP3 files with the FileMon utility from www.sysinternals.com.

I had a bunch of directories shared and I went into the preferences and unshared a few directories and after that, LimeWire began scanning files in the directories I had just unshared. It doesn't make any sense why it would do that.

The other thing I noticed is the order that it was scanning the files. It was jumping from one drive to another, seemingly at random. This is probably an artifact of the Java hashing class that is used to store the list of shared files. I would think this would make my drive work harder as it's seeking to the inside and back to the outside of the disk as it jumps from one file to the next.

So, I'm requesting that the apparent bug of scanning files that have been unshared be fixed. And I request that the bitrate scan be optimized to scan the files in a directory sequentially instead of randomly scanning files in different directories on different drives.