All of lore.kernel.org
 help / color / mirror / Atom feed
From: "Dieter Stüken" <stueken@conterra.de>
To: LVM general discussion and development <linux-lvm@redhat.com>
Subject: Re: [linux-lvm] LVM incredible slow with Kernel 2.6.11
Date: Thu, 29 Jun 2006 18:15:23 +0200	[thread overview]
Message-ID: <44A3FC9B.3070500@conterra.de> (raw)
In-Reply-To: <20060629144606.GG20554@vwclub.ro>

Cristian Livadaru wrote:
> me again ... isn't there anybody that could give ANY hint on what's
> wrong?
> 
> I did some test with dd and the result is terrible!
> 
> LVM
> explendidos:/shared# dd if=/dev/zero of=test1.dd bs=64 count=1000
> 1000+0 records in
> 1000+0 records out
> 64000 bytes transferred in 20.019969 seconds (3197 bytes/sec)

seems the data gets written synchronously without any buffering.
Thus each write is delayed until the data is really written to
disk. For a 5400 RPM disk you get 90 transactions per seconds.
This gives about 10 seconds for 1000 chunks. "bs=64" means
64 bytes! so each sector will be written multiple times.
So may be the system even reads in each sector again each time
before writing it, thus it takes two turns which gives 20 seconds.

Unfortunately I can't tell why this happens :-(

May be "direct IO" takes place (like for oflags=direct),
or this is some configuration option of LVM, i don't know about.
Try using "hdparm" to see, if DMA etc. is enabled. Have a look
into /var/log/messages or use "dmesg" for nay hardware problems.
I recently discovered the "blockdev" command. Do you use any special
ext3 feature? You may try "tune2fs -o journal_data_writeback".
If you don't have relevant data on the LV, you may try to write
to the LV device directly. Is it slow for read, too? try "hdparm -t"

Dieter.

  reply	other threads:[~2006-06-29 16:15 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2006-06-28  9:24 [linux-lvm] LVM incredible slow with Kernel 2.6.11 Cristian Livadaru
2006-06-29 14:46 ` Cristian Livadaru
2006-06-29 16:15   ` Dieter Stüken [this message]
2006-06-30  7:32     ` Cristian Livadaru
2006-06-30 12:32       ` Cristian Livadaru

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=44A3FC9B.3070500@conterra.de \
    --to=stueken@conterra.de \
    --cc=linux-lvm@redhat.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.