From: Andrew Patterson <andrew@fc.hp.com>
To: linux-lvm@sistina.com
Cc: "Heinz J . Mauelshagen" <mauelshagen@sistina.com>
Subject: Re: [linux-lvm] Oops when running snapshots
Date: Thu Jul 10 12:28:02 2003 [thread overview]
Message-ID: <1057858065.1368.32.camel@lvadplx> (raw)
In-Reply-To: <20030710113223.D23240@sistina.com>
On Thu, 2003-07-10 at 03:32, Heinz J . Mauelshagen wrote:
> On Wed, Jul 09, 2003 at 04:26:36PM -0600, Andrew Patterson wrote:
> > Ran a load test last night where we created snapshots two snapshots
> > every 2 hours under heavy file system load. We got the following oops:
> >
> >
> > Unable to handle kernel NULL pointer dereference at virtual address
> > 00000000
> > 802895f5
> <SNIP>
> > 11: 89 48 04 mov %ecx,0x4(%eax)
> >
> >
> > 10 warnings issued. Results may not be reliable.
> >
> > This was run on a 2.4.21 system using LVM 1.0.7. The system has 2GB of
> > memory and is configured with HIGHME64G. We are running the latest
> > 2.4.21 XFS and are using xfs_freeze to quiesce the file system. We are
> > not using the VFS_LOCK patch.
> >
> > Anyone have any ideas what may be causing this?
>
> VM problems ? (we had some reports ITR)
> Do you have a chance to retest without HIGHMEM to see if it still fails ?
>
I looked through mailing list archives about this. Most the of himem
problems resulted in vmmalloc.c calls in the oops. I'll try it again
without himem to see if this helps.
Thanks,
Andrew
> >
> > Thanks,
next prev parent reply other threads:[~2003-07-10 12:28 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2003-07-09 17:27 [linux-lvm] Oops when running snapshots Andrew Patterson
2003-07-10 4:34 ` Heinz J . Mauelshagen
2003-07-10 12:28 ` Andrew Patterson [this message]
2003-08-15 17:16 ` Andrew Patterson
-- strict thread matches above, loose matches on Subject: below --
2004-01-05 4:36 Steve McIntyre
2004-01-12 9:36 ` Steve McIntyre
2004-01-14 8:37 ` Andrew Patterson
2004-01-21 5:35 ` Steve McIntyre
2004-01-12 10:27 Little, Chris
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=1057858065.1368.32.camel@lvadplx \
--to=andrew@fc.hp.com \
--cc=linux-lvm@sistina.com \
--cc=mauelshagen@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