From: Gregory 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: Thu Oct 31 16:55:02 2002 [thread overview]
Message-ID: <1036104859.21418.104.camel@pslgregory> (raw)
In-Reply-To: <20021031134804.A491@sistina.com>
[-- Attachment #1: Type: text/plain, Size: 1392 bytes --]
On Thu, 2002-10-31 at 04:48, Heinz J . Mauelshagen wrote:
> Gregory a _different_ system is unlikely to help.
> I was asking for changes to take affect on the system where you do have
> the problem.
Ahh... That may take a little time, then. I can certainly prepare
another kernel for testing with high memory support turned off, and try
to do some tests at the end of business on friday. It might have to
wait a little longer, though. I'll see what they're willing to
schedule, and get you results when I can.
> If you have a chance to reconfigure the failing system temporarily,
> running what you did before should reproduce the same problems (segfault
> on snapshot creation after fresh reboot) in case there's _no_ bug in the
> large/high memory support.
> My assumption is that it will not.
So, just for clarification, on the system where I am having this
problem, all you want me to do is run a kernel without high memory
support and attempt the snapshot creation? Unfortunately, the way the
system was assembled, the smallest I can physically reduce the RAM to is
4GB (two DIMMS on each memory carrier is the minimum required for the
system to boot, and they shipped it to us with 8 1GB DIMMS.)
Thanks again,
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: 232 bytes --]
next prev parent reply other threads:[~2002-10-31 16:55 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 [this message]
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=1036104859.21418.104.camel@pslgregory \
--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