diff options
-rw-r--r-- | crc32.c | 0 | ||||
-rw-r--r-- | crc32.h | 0 | ||||
-rwxr-xr-x[-rw-r--r--] | inventory | 0 | ||||
-rw-r--r-- | md.4 | 7 | ||||
-rw-r--r-- | super-ddf.c | 0 |
5 files changed, 7 insertions, 0 deletions
diff --git a/crc32.c b/crc32.c deleted file mode 100644 index e69de29..0000000 --- a/crc32.c +++ /dev/null diff --git a/crc32.h b/crc32.h deleted file mode 100644 index e69de29..0000000 --- a/crc32.h +++ /dev/null diff --git a/inventory b/inventory index 1d8e25b..1d8e25b 100644..100755 --- a/inventory +++ b/inventory @@ -168,6 +168,13 @@ All devices in a RAID1 array should be the same size. If they are not, then only the amount of space available on the smallest device is used (any extra space on other devices is wasted). +Note that the read balancing done by the driver does not make the RAID1 +performance profile be the same as for RAID0; a single stream of +sequential input will not be accelerated (e.g. a single dd), but +multiple sequential streams or a random workload will use more than one +spindle. In theory, having an N-disk RAID1 will allow N sequential +threads to read from all disks. + .SS RAID4 A RAID4 array is like a RAID0 array with an extra device for storing diff --git a/super-ddf.c b/super-ddf.c deleted file mode 100644 index e69de29..0000000 --- a/super-ddf.c +++ /dev/null |