Linux LVM users
 help / color / mirror / Atom feed
From: "Gregory K. Ade" <gkade@bigbrother.net>
To: linux-lvm@sistina.com
Subject: Re: [linux-lvm] strange behavior with 1.0.5 on Linux 2.4.19?
Date: Tue Oct 29 13:54:02 2002	[thread overview]
Message-ID: <1035921224.1276.24.camel@gopher> (raw)
In-Reply-To: <20021029101033.A22193@sistina.com>

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

On Tue, 2002-10-29 at 01:10, Heinz J . Mauelshagen wrote:
> 
> Gregory,
> 
> as Jon already thought, this seems to be a flaw in the VM subsystem.
> 
> The ksymoops you provided shows that, because it fails in vmalloc when
> lvm_snapshot_alloc_hash_table() tries to allocated virtual memory for the
> copy-on-write exeception table it needs to track the changes which happen
> to the original logical volume.
> 
> Is there any chance to prove that by running the system with less than 2GB
> of memory and _without_ high memory support for a test run?
> 
> Regards,
> Heinz    -- The LVM Guy --

Actually, yes, I can run this on several other smaller-memory systems. 
I've got a machine I've been working on setting up that's 2GB exactly,
and several others running 2.4.19 & LVM 1.0.5 with less than 1GB of
ram.  However, I've not had any of these systems produce errors like
these.  I can run the 2GB system with and without high memory support
and try to induce a similar failure.

Are there any specific tests you'd like me to run on this other system,
in case I can't induce an Oops on it?

Thanks,

Gregory

-- 
Gregory K. Ade <gkade@bigbrother.net>
http://bigbrother.net/~gkade
OpenPGP Key ID: EAF4844B  keyserver: pgpkeys.mit.edu

[-- Attachment #2: This is a digitally signed message part --]
[-- Type: application/pgp-signature, Size: 189 bytes --]

  reply	other threads:[~2002-10-29 13:54 UTC|newest]

Thread overview: 21+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2002-10-02 12:23 [linux-lvm] strange behavior with 1.0.5 on Linux 2.4.19? Gregory K. Ade
2002-10-04  3:54 ` Heinz J . Mauelshagen
2002-10-08 15:07   ` Gregory Ade
2002-10-09  6:38     ` Heinz J . Mauelshagen
2002-10-27 22:30       ` Gregory K. Ade
2002-10-28  3:21         ` Heinz J . Mauelshagen
2002-10-28 22:38           ` Gregory K. Ade
2002-10-29  3:15             ` Heinz J . Mauelshagen
2002-10-29 13:54               ` Gregory K. Ade [this message]
2002-10-31  6:52                 ` Heinz J . Mauelshagen
2002-10-31 16:55                   ` Gregory Ade
2002-11-01  9:07                     ` Wolfgang Weisselberg
2002-11-05  8:33                     ` Heinz J . Mauelshagen
2002-11-07 21:45                       ` Gregory Ade
2002-11-09  6:12                         ` Heinz J . Mauelshagen
2002-11-11  5:56                           ` Jon Bendtsen
2002-11-22 15:51                           ` Gregory Ade
2002-12-05 21:35                           ` Gregory Ade
2002-10-28 14:36         ` jon+lvm
2002-10-28 16:40           ` Gregory K. Ade
2002-10-29 15:21             ` Luca Berra

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=1035921224.1276.24.camel@gopher \
    --to=gkade@bigbrother.net \
    --cc=linux-lvm@sistina.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