* Koerner, Sebastian textete am 07.05.03:
Dazu hätte ich mal eine Frage: ich habe mal einen "hdparm -i /dev/md0" ausgeführt. Dabei kommt mein ZCyber RAID Controller mit Software RAID 0 auf magere 37,87MBsec (Timing buffer-cache reads). (2x IBM DTLA-307015, ZCyber 133 RAID Controller und ASUS T2P4 Board mit AMD K6II-400.
Nanu, wurde da was bei hdparm geändert? HDPARM(8) HDPARM(8) -i Display the identification info that was obtained from the drive at boot time, if available. This is a feature of modern IDE drives, and may not be sup ported by older devices. The data returned may or may not be current, depending on activity since booting the system. However, the current multiple sector mode count is always shown. For a more detailed interpretation of the identification info, refer to AT Attachment Interface for Disk Drives (ANSI ASC X3T9.2 working draft, revision 4a, April 19/93). Damit mißt du Übertragungsraten? Meinst du nicht eher: -T Perform timings of cache reads for benchmark and comparison purposes. For meaningful results, this operation should be repeated 2-3 times on an other wise inactive system (no other active processes) with at least a couple of megabytes of free memory. This displays the speed of reading directly from the Linux buffer cache without disk access. This measurement is essentially an indication of the throughput of the processor, cache, and memory of the system under test. If the -t flag is also specified, then a correction factor based on the outcome of -T will be incorporated into the result reported for the -t operation. -t Perform timings of device reads for benchmark and comparison purposes. For meaningful results, this operation should be repeated 2-3 times on an other wise inactive system (no other active processes) with at least a couple of megabytes of free memory. This displays the speed of reading through the buffer cache to the disk without any prior caching of data. This measurement is an indication of how fast the drive can sustain sequential data reads under Linux, without any filesystem overhead. To ensure accurate measurments, the buffer cache is flushed during the processing of -t using the BLK FLSBUF ioctl. If the -T flag is also specified, then a correction factor based on the outcome of -T will be incorporated into the result reported for the -t operation. hdparm - get/set hard disk parameters - version v4.1 Hat sich da echt was geändert?
Und ich erhalte ein "Suspicious Result: probably not enough free Memory". Hier sind aber 73KB physischer Speicher frei und auf dem zu testenden Raid sind noch 18GByte von 28GByte frei.
Du schreibst von ca. 7300 Byte freiem physischem Speicher. Was ist bei dir physischer Speicher? Auf deinem Raid sind nach deiner Aussage ca. 10.000.000.000 Byte frei. Irgendwie verwirrt mich deine mail etwas... cu flo -- Ich hatte bis vor kurzem auch immer geglaubt das Mädchen böse Jungens seien denen der liebe Gott Den "Pieselmann" weggenommen hatt. Und das mit den Busen wurde mior auch erst vor wenigen Jahren klar. [WoKo in dag°]