linux-lvm.redhat.com archive mirror
 help / color / mirror / Atom feed
From: Micky <mickylmartin@gmail.com>
To: Marian Csontos <mcsontos@redhat.com>
Cc: Zdenek Kabelac <zkabelac@redhat.com>,
	LVM general discussion and development <linux-lvm@redhat.com>
Subject: Re: [linux-lvm] Very slow i/o after snapshotting
Date: Tue, 9 Jul 2013 20:39:49 +0500	[thread overview]
Message-ID: <CAKAA-nms7a9tG4cGiSV4MDaCzF-6+fdpPaOjzBEmdNtxUcPMCA@mail.gmail.com> (raw)
In-Reply-To: <CAKAA-nmRjbBN1T9g=fwhJQGyriOJK4vR7L2uQzAFw5maPKFEMQ@mail.gmail.com>

I meant alignment for all dm entries 0 through 31 is zero!


>> What does the `lsblk -t` say? Could be an alignment issue.
>
> 0 through 31
>
>> What's `free` saying about the free memory and cache? (dmeventd on 6.4 is
>> trying to lock a large chunk of address space in RAM (~100M)
>
> Cached mem looks good.
> Dmeventd. Right. It is. Isn't it spawed everytime an LV is created?
> root      6813  0.0  1.4 197056 11044 ?        S<s  May26   2:44 /sbin/dmeventd

  reply	other threads:[~2013-07-09 15:39 UTC|newest]

Thread overview: 21+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2013-07-09  1:37 [linux-lvm] Very slow i/o after snapshotting Micky
2013-07-09  5:01 ` Marian Csontos
2013-07-09  8:26   ` Micky
2013-07-09  9:54 ` Zdenek Kabelac
2013-07-09 11:51   ` Micky
2013-07-09 12:19     ` Marian Csontos
2013-07-09 12:43       ` Micky
2013-07-09 13:20         ` Zdenek Kabelac
2013-07-09 14:04           ` Micky
2013-07-09 14:18             ` Zdenek Kabelac
2013-07-09 14:57               ` Micky
2013-07-09 15:14                 ` Zdenek Kabelac
2013-07-09 15:26                   ` Micky
2013-07-09 15:26                 ` Marian Csontos
2013-07-09 15:35                   ` Micky
2013-07-09 15:39                     ` Micky [this message]
2013-07-09 18:47                       ` Zdenek Kabelac
2013-07-09 23:15                         ` Micky
2013-07-09 23:29                           ` Micky
2013-07-09 17:59           ` matthew patton
2013-07-09 18:42             ` 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=CAKAA-nms7a9tG4cGiSV4MDaCzF-6+fdpPaOjzBEmdNtxUcPMCA@mail.gmail.com \
    --to=mickylmartin@gmail.com \
    --cc=linux-lvm@redhat.com \
    --cc=mcsontos@redhat.com \
    --cc=zkabelac@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).