From: Spam <spam@tnonline.net>
To: neuron <linux-lvm@sistina.com>
Subject: Re: [linux-lvm] Performance problem.
Date: Mon Nov 17 12:45:02 2003 [thread overview]
Message-ID: <6557103468.20031117194401@tnonline.net> (raw)
In-Reply-To: <20031117193054.5dd7eec1.neuron@hollowtube.mine.nu>
>> No, that is true. Your low read speed does indicate that you are
>> not using DMA. Give us the output of "hdparm /dev/hda". Also a
>> simple benchmark is to do "dd_rescue /dev/hda /dev/null". What does
>> that give you in numbers?
> /dev/hdd:
> multcount = 16 (on)
> IO_support = 1 (32-bit)
> unmaskirq = 0 (off)
> using_dma = 1 (on)
> keepsettings = 0 (off)
> readonly = 0 (off)
> readahead = 8 (on)
> geometry = 14589/255/63, sectors = 234375000, start = 0
This looks good. You could try -c3 to enable 32-bit w/sync and also
enable Write cache -W1 (this may and many not be wise in case you
have power failures often).
> the cables are new (I thought that they may be a problem), I've
> gotten far better speeds on the same system and a worse system
> before I used lvm on the same drives. I REALLY doubt there's
> something wrong with the drives (I replaced one of them because of
> an error, and looked for trouble after replacing that one, but
> didn't find anything else).
> And that dd_rescue will read from /dev/hda and write to /dev/null
> right? Meaning it's a read test, and not a write test (= I won't
> loose any data on it ;) ).
Yes, it is a read-only test! Read the manpage to get all flags you
can use with it (such as how big blocks it is to read etc).
> _______________________________________________
> linux-lvm mailing list
> linux-lvm@sistina.com
> http://lists.sistina.com/mailman/listinfo/linux-lvm
> read the LVM HOW-TO at http://tldp.org/HOWTO/LVM-HOWTO/
next prev parent reply other threads:[~2003-11-17 12:45 UTC|newest]
Thread overview: 32+ messages / expand[flat|nested] mbox.gz Atom feed top
2003-11-14 6:28 [linux-lvm] Performance problem neuron
2003-11-14 6:54 ` Henric Andersson
2003-11-14 6:59 ` neuron
2003-11-16 17:50 ` neuron
2003-11-17 10:36 ` Jean-louis MATTON
2003-11-17 10:53 ` neuron
2003-11-17 10:54 ` Austin Gonyou
2003-11-17 11:00 ` neuron
2003-11-17 11:40 ` Michael Paesold
2003-11-17 11:12 ` neuron
2003-11-17 11:36 ` Spam
2003-11-17 12:15 ` neuron
2003-11-17 12:24 ` Spam
2003-11-17 12:32 ` neuron
2003-11-17 12:45 ` Spam [this message]
2003-11-17 12:54 ` neuron
2003-11-17 13:02 ` Spam
2003-11-17 13:07 ` neuron
2003-11-17 16:56 ` Henric Andersson
2003-11-17 18:45 ` Spam
2003-11-17 19:07 ` neuron
2003-11-17 19:18 ` Spam
2003-11-17 19:44 ` neuron
2003-11-18 8:14 ` Henric Andersson
2003-11-18 8:44 ` neuron
2003-11-18 9:02 ` Henric Andersson
2003-11-18 9:07 ` neuron
2003-11-18 17:43 ` Henric Andersson
2003-11-18 18:03 ` neuron
2003-11-19 7:22 ` Henric Andersson
2003-11-17 14:01 ` Michael Paesold
2003-12-27 23:31 ` Steven Lembark
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=6557103468.20031117194401@tnonline.net \
--to=spam@tnonline.net \
--cc=linux-lvm@sistina.com \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.