linux-lvm.redhat.com archive mirror
 help / color / mirror / Atom feed
From: Andre Noll <maan@systemlinux.org>
To: Alasdair G Kergon <agk@redhat.com>
Cc: dm-devel@redhat.com,
	LVM general discussion and development <linux-lvm@redhat.com>,
	Heinz Mauelshagen <mauelshagen@redhat.com>
Subject: [linux-lvm] more than 10 shapshots freeze system
Date: Mon, 12 Feb 2007 18:47:02 +0100	[thread overview]
Message-ID: <20070212174702.GG19569@skl-net.de> (raw)

[-- Attachment #1: Type: text/plain, Size: 1539 bytes --]

Hi

last week I was experimenting a bit with lvm snapshots. What I tried
to do was to create 2 snapshots per day from our ~5T "backup" ext3
filesystem which gets rsynced twice a day from the (remote) "real"
production filesystem.

Our workload changes at most 50G of data a day, so I chose an initial
snapshot size of 50G. After each rsync run, the snapshot lvs were
extended so that each of them had again 50G free space available.

This worked very well for about three days, i.e. six snapshots. From
this day on, the system [1] became more and more sluggish during
the rsync runs. Hitting return in bash on the otherwise idle system
began to take as much as several seconds. Simple lvm commands like
lvdisplay took up to several minutes.

Two or three days later (i.e. 10+ snapshots) the system froze totally
during the rsync. Nothing made it to the system log. I could easily
reproduce this by running rsync again or by simply creating a 100M
file.

Is this an expected behaviour?

If so, is there a formula in terms of filesytem/snapshot/ram size to
compute the maximal number of snapshots that may be created from the
same filesystem without risking to freeze the system?

If this behaviour is not expected, what can I do to improve the
situation or to debug this problem?

Thanks
Andre

[1] HP Proliant, 2-way AMD Opteron, 5G Ram, linux-2.6.19.x and
linux-2.6.20, ubuntu server lvm tools based on libdevmapper-1.02
-- 
The only person who always got his work done by Friday was Robinson Crusoe

[-- Attachment #2: Digital signature --]
[-- Type: application/pgp-signature, Size: 189 bytes --]

             reply	other threads:[~2007-02-12 17:47 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2007-02-12 17:47 Andre Noll [this message]
2007-02-28 17:45 ` [linux-lvm] Re: INFO: possible recursive locking detected. Was: more than 10 shapshots freeze system Andre Noll

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=20070212174702.GG19569@skl-net.de \
    --to=maan@systemlinux.org \
    --cc=agk@redhat.com \
    --cc=dm-devel@redhat.com \
    --cc=linux-lvm@redhat.com \
    --cc=mauelshagen@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).