linux-lvm.redhat.com archive mirror
 help / color / mirror / Atom feed
From: Stuart D Gathman <stuart@bmsi.com>
To: linux-lvm@redhat.com
Subject: Re: [linux-lvm] LVM commands extremely slow during raid check/resync
Date: Wed, 28 Mar 2012 14:26:11 -0400	[thread overview]
Message-ID: <4F7357C3.4060205@bmsi.com> (raw)
In-Reply-To: <4F72C38E.2080806@redhat.com>

Long ago, Nostradamus foresaw that on 03/28/2012 03:53 AM, Zdenek 
Kabelac would write:
> It seems that your cfq scheduler should be tuned better for raid 
> arrays - I assume you allow the system to create very large queues of 
> buffers and your mdraid isn't fast enough to store dirty pages on disk 
> - I'd probably suggest to significantly lower the maximum amount of 
> dirty pages - as creation of snapshot requires fs sync operation it 
> will need to wait till all buffers before the operation are in place.
A question (or minor nit): how could lvm possibly require a fs sync to 
create a snapshot?  I could see this for Xen, where guest OS has to 
support a com channel to host.  But for full virtualization, LVM doesn't 
know in general what OS is running, or how to suggest an FS sync.  Or is 
this something an admin does, run a script that tells guest to sync 
before creating shapshot through lvm (to maximize the amount of useful 
data in the snapshot)?

  reply	other threads:[~2012-03-28 18:26 UTC|newest]

Thread overview: 14+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2012-03-25  7:56 [linux-lvm] LVM commands extremely slow during raid check/resync Larkin Lowrey
2012-03-26 13:02 ` James Candelaria
2012-03-26 17:49   ` Larkin Lowrey
2012-03-26 20:55 ` Ray Morris
2012-03-26 23:51   ` Larkin Lowrey
2012-03-27 14:34     ` Zdenek Kabelac
2012-03-27 21:24       ` Larkin Lowrey
2012-03-28  7:53         ` Zdenek Kabelac
2012-03-28 18:26           ` Stuart D Gathman [this message]
2012-03-29  0:27             ` Ray Morris
2012-03-29  9:48             ` Zdenek Kabelac
2012-03-27 14:31   ` Zdenek Kabelac
2012-03-27 18:11     ` Ray Morris
2012-03-27 20:36       ` Zdenek Kabelac

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=4F7357C3.4060205@bmsi.com \
    --to=stuart@bmsi.com \
    --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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).