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: Mon Oct 28 16:40:01 2002 [thread overview]
Message-ID: <1035844780.9075.64.camel@gopher> (raw)
In-Reply-To: <20021028203549.GA24302@gw.silicide.dk>
[-- Attachment #1: Type: text/plain, Size: 1809 bytes --]
On Mon, 2002-10-28 at 12:35, jon+lvm@silicide.dk wrote:
> On Sun, Oct 27, 2002 at 09:29:35PM -0800, Gregory K. Ade wrote:
>
> [cut]
>
> > So, who do I give what information to so that we can trace down the base
> > of this problem, and get a fix? Ask me for whatever you need from the
> > system, and I'll provide it if I can.
>
> I dont know what your problem is, but i run lvm 1.0.5 on a default 2.4.19
> without trouble. (any more).
> I lvcreate once an hour, though it is a snapshot, and remove it again
> the next hour. I've got a script running every minute that extends the
> snapshots if they become too small. So, maybe the problem isnt in lvm, but
> memory, and it just happens to hit LVM ?
Interesting that you should mention this. This system has proved to
have several interesting quirks, and most of them that have been
resolved have been resolved by making patches or other fixes in
relationship to the large memory configuration (8GB). System
performance issues related to the filesystems were actually resolved by
applying a VM/VFS patch (I'm not really sure what it patched, honestly)
that was specifically addressing problems in >2GB RAM systems.
Is it possible that similar issues may be present in LVM? How many
people here are running LVM on systems with ~100GB available storage or
more and 4GB or more of RAM?
This is the only system exhibiting these problems. Then again, this is
the only system that requires highmem (64GB) support in order to address
all the memory, too.
I'll be able to generate a ksymoops sometime tonight, which will
hopefully point the LVM developers in the right direction for a fix.
--
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 --]
next prev parent reply other threads:[~2002-10-28 16:40 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
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 [this message]
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=1035844780.9075.64.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.