From: Tomasz Chmielewski <mangoo@wpkg.org>
To: LVM general discussion and development <linux-lvm@redhat.com>
Subject: Re: [linux-lvm] "cannot allocate memory" when trying to do a snapshot?
Date: Sat, 01 Sep 2007 22:39:25 +0200 [thread overview]
Message-ID: <46D9CDFD.7010800@wpkg.org> (raw)
In-Reply-To: <1188232446.24432.3.camel@pc.ilinx>
Brian J. Murrell schrieb:
> On Mon, 2007-08-27 at 18:25 +0200, Tomasz Chmielewski wrote:
>> Looks like it's here:
>>
>> https://bugzilla.redhat.com/show_bug.cgi?id=208172
>
> Yup. That's the one my bug 191531 was dup'd to.
>
>> Let's see if upgrading the kernel helps...
>
> Let us know.
It looks that it helped.
However, now it's possible to create a snapshot that is no longer
possible to remove...
See my other thread ("how much memory does LVM need? oom-killer comes").
--
Tomasz Chmielewski
http://wpkg.org
prev parent reply other threads:[~2007-09-01 20:39 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-08-24 14:11 [linux-lvm] "cannot allocate memory" when trying to do a snapshot? Tomasz Chmielewski
2007-08-27 16:08 ` Tomasz Chmielewski
2007-08-27 16:14 ` Brian J. Murrell
2007-08-27 16:25 ` Tomasz Chmielewski
2007-08-27 16:34 ` Brian J. Murrell
2007-09-01 20:39 ` Tomasz Chmielewski [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=46D9CDFD.7010800@wpkg.org \
--to=mangoo@wpkg.org \
--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).