From: Paul Warren <pdw@ex-parrot.com>
To: LVM general discussion and development <linux-lvm@redhat.com>
Subject: Re: [linux-lvm] "Cannot allocate memory" creating VGDA
Date: Sat, 16 Oct 2004 20:49:48 +0100 [thread overview]
Message-ID: <20041016204948.M28225@sphinx.mythic-beasts.com> (raw)
In-Reply-To: <20041016154045.G28225@sphinx.mythic-beasts.com>; from pdw@ex-parrot.com on Sat, Oct 16, 2004 at 03:40:45PM +0100
On Sat, Oct 16, 2004 at 03:40:45PM +0100, Paul Warren wrote:
> Varying the chunk size doesn't seem to help. This appears to be the
> HIGHMEM issue that has come up on the list before. If we recompile the
> kernel without HIGHMEM support, it works OK (apart from the
> unavailability of 3/4 of the RAM).
>
> We're running 2.4.27 - are there patches beyond that?
>
> Has anyone had any success with getting snapshots to work on a machine
> with > 1GB RAM?
It seems that this works if you compile the kernel with HIGHMEM 64G
support or with HIGHMEM off, but not with 4G support.
Paul
prev parent reply other threads:[~2004-10-16 19:49 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-10-16 10:05 [linux-lvm] "Cannot allocate memory" creating VGDA Paul Warren
2004-10-16 13:09 ` Alasdair G Kergon
2004-10-16 14:40 ` Paul Warren
2004-10-16 19:49 ` Paul Warren [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=20041016204948.M28225@sphinx.mythic-beasts.com \
--to=pdw@ex-parrot.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