On Saturday 29 January 2005 02:39 pm, Pieter Hulshoff wrote:
On Saturday 29 January 2005 20:25, Randall R Schulz wrote:
How about showing us actual output from hdparam. Not only from the speed test options, but from the device information options, too. There may be some clues therein. hdparm -v -i -t /dev/hda
Ok, I ran this on /dev/hda, /dev/hda3, /dev/hda4, /dev/hdc, /dev/hdc3, and /dev/hdc4, and below's the output. Since I'm doing this from a running system, results will be lower than indicated in previous emails (got a few other programs running as well right now; if needs be I'll run this from a recue disk later to get you unmounted performance; hda and hdc are about equally used (software RAID) so the relative performance should be ok).
/dev/hda: multcount = 16 (on) IO_support = 1 (32-bit) unmaskirq = 1 (on) using_dma = 1 (on) keepsettings = 0 (off) readonly = 0 (off) readahead = 256 (on) geometry = 19929/255/63, sectors = 320173056, start = 0 [...] Regards,
Pieter Hulshoff =========
Pieter, Sorry, I haven't been following this thread closely, but saw something that threw up a red flag. I thought I would at least suggest it to you at this point. I notice that you have IO_support = 1 (32-bit). First question/suggestion is do you have an ATA100/133 cable connected to the drive? That's the one with 80 wires, but still 40 pins. Second, have you tried changing that bit to 0 (16-bit)? I think you might see a difference in your readings. Test with hdparm -T /dev/hdx & hdparm -t /dev/hdx, as that will give you both cache read & drive read speeds. I know you can set the IO_support setting with hdparm -c0 (16-bit) or -c1 (32-bit). Also, in checking my settings, I notice that unmaskirq is 0 (off) as well. Sorry, don't remember the option to change that, just do "hdparm --help" for all your options. hopefully helpful, Lee -- --- KMail v1.7.2 --- SuSE Linux Pro v9.2 --- Registered Linux User #225206 "Don't let the fear of striking out keep you from playing the game!"