From: Brian Weck <bweck@weck.net>
To: linux-lvm@redhat.com
Subject: [linux-lvm] snapshot, machine hang and physical memory required
Date: Tue, 07 Mar 2006 16:13:21 -0500 [thread overview]
Message-ID: <440DF771.1050506@weck.net> (raw)
I seem to be encountering a problem when attempting to create a
snapshot. Sometimes the snapshot goes through fine and at other times
while executing a 'lvcreate --snapshot ...' it subsequently causes my
box to hang completely.
From what I've read, this problem seems to be related to having
insufficient physical memory.
I can not seem to find where/how to estimate how much memory is required
to successfully perform the snapshot. Is the memory required relative to
the snapshot size, the size of the target LVM device or both?
I'm running with a 2.6.12 kernel:
lvm2-2.01.14-2.0.RHEL4
device-mapper-1.01.04-1.0.RHEL4
As the machine seems to hang when creating a snapshot on "/" (rather the
logical volume upon which "/" resides), upon a reboot I do not see
anything in my logs related to the problem which further makes the
problem harder to debug.
Any help would be greatly appreciated-
Brian
reply other threads:[~2006-03-07 21:13 UTC|newest]
Thread overview: [no followups] expand[flat|nested] mbox.gz Atom feed
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=440DF771.1050506@weck.net \
--to=bweck@weck.net \
--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).