What is the difference between a volume set and disk striping? How does Diskeeper work with them?
A volume set is designed to allow many disks to appear as one disk, so that files larger than any one of the disks can be laid out over multiple disks. Disk striping is a little different in that it was designed to increase the I/O speed to disk. Let's say you have a five-disk stripe set. With some exceptions, a file written to this stripe set will consist of five pieces, with each piece residing on a separate physical disk. Reading such a file can occur up to five times as fast as it would if the file was only on one disk. Writing to disk can be five times as fast, too. Generally, the more disks in the stripe set, the faster the disk I/O. In a volume set you could have five disks, but the files would not be forced to lay out over five different physical disks. Smaller files could reside on one disk, and huge files could be spread out over multiple disks, depending on the size of the file and available disk space. Disk I/O performance is not necessarily increased in volume sets, but is the key issue in disk striping. When using Diskeeper to defragment a volume set, you would specify each individual member of the volume set. Diskeeper will only defragment data on a disk basis. In other words, if a file is laid out over two different physical disks, Diskeeper will not cross over physical disk boundaries and put the entire file on one disk. Each physical disk in the volume set is defragmented individually. When using Diskeeper to defragment a stripe set, you would ONLY specify the logical name associated with the stripe set. You must be careful NOT to specify any member of the stripe set individually, and only specify the logical name.
If this FAQ helped, please let us know. If you didn't find the answer to your question here please e-mail
|
