From: Alasdair G Kergon <agk@redhat.com>
To: LVM general discussion and development <linux-lvm@redhat.com>
Subject: Re: [linux-lvm] vgchange -ay Killed
Date: Sat, 29 Apr 2006 23:24:53 +0100 [thread overview]
Message-ID: <20060429222453.GC16180@agk.surrey.redhat.com> (raw)
In-Reply-To: <445394B9.6040104@volved.com>
The code has not been optimised for large numbers of LVs.
Use the latest dm/lvm2 versions for a start as there's a memory
leak in your libdevmapper.
Each device device uses up a fixed amount of (unswappable) kernel
memory, and when all your memory is used out you can't have any
more devices.
Use standard diagnostic tools to work out which limit you're hitting.
(top; ps; slabtop; sysreq; strace etc.)
Alasdair
next prev parent reply other threads:[~2006-04-29 22:24 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-04-28 16:10 [linux-lvm] vgchange -ay Killed Ming Zhang
2006-04-28 22:09 ` Jonathan E Brassow
2006-04-28 22:10 ` Ming Zhang
2006-04-29 16:30 ` Barnaby Claydon
2006-04-29 22:24 ` Alasdair G Kergon [this message]
2006-04-29 22:58 ` Ming Zhang
[not found] ` <e651e1f7ae134a3bddcd370a7e29119d@redhat.com>
[not found] ` <1146323005.15799.8.camel@localhost.localdomain>
2006-04-29 21:56 ` Ming Zhang
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=20060429222453.GC16180@agk.surrey.redhat.com \
--to=agk@redhat.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).