All of lore.kernel.org
 help / color / mirror / Atom feed
From: Marian Csontos <mcsontos@redhat.com>
To: LVM general discussion and development <linux-lvm@redhat.com>
Cc: Andres Toomsalu <andres@opennodecloud.com>
Subject: Re: [linux-lvm] Slow boot with large number of thin snapshots
Date: Tue, 12 Feb 2013 12:57:08 +0100	[thread overview]
Message-ID: <511A2E14.6060907@redhat.com> (raw)
In-Reply-To: <AF6C40D9-3087-4B95-97A3-8E056C2497A0@opennodecloud.com>

On 02/07/2013 01:42 PM, Andres Toomsalu wrote:
> Hi,
>
> We have experienced a situation where we are left with large number
> of thin snapshots (around 500) and snapshot removal wont work anymore
> (we suspect a lock-up situation caused by trying to remove thin
> snapshots that is still mounted - thou  its not verified yet - just a
> speculation).  The only path to recover seems to be disabling all
> thin volumes from fstab and booting into single-user mode - where
> lvremove -f usually succeeds on these thin snapshots. But LVM init
> and lvremove take a huge amount of time with large number of
> snapshots  - initial LVM activation is going on about 6-8 minutes at
> least and every lvremove takes ca 20-50 sec - depending on snapshot
> count left. After snapshots are removed thin volumes can be enabled
> again and fsck-ed and resuming normal operations.

Hello Andres, could you provide the following information:

Which version of lvm?
Is lvmetad used?

     grep lvmetad /etc/lvm/lvm.conf
     pgrep lvmetad

RHEL6.3 version of lvmetad had a serious performance issue with many 
[thin] snapshots, which should be solved in the latest release 
(lvm2-2.02.98)

Could you check the memory usage while the command is running?

Also there were a high memory usage problems fixed in the recent version.

-- Marian

>
> Althou we are not yet sure what is causing the lockup - so that
> snapshots cant be removed anymore without reboot - its also
> problematic that with large numbers of snapshots all LVM device
> operations are dead slow.  I hope this issue can be addressed somehow
> in the future.
>
> Kind regards,
>
>
>
> _______________________________________________ linux-lvm mailing
> list linux-lvm@redhat.com
> https://www.redhat.com/mailman/listinfo/linux-lvm read the LVM HOW-TO
> at http://tldp.org/HOWTO/LVM-HOWTO/

      reply	other threads:[~2013-02-12 11:57 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2013-02-07 12:42 [linux-lvm] Slow boot with large number of thin snapshots Andres Toomsalu
2013-02-12 11:57 ` Marian Csontos [this message]

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=511A2E14.6060907@redhat.com \
    --to=mcsontos@redhat.com \
    --cc=andres@opennodecloud.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 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.