All of lore.kernel.org
 help / color / mirror / Atom feed
From: "James A. Pattie" <james@pcxperience.com>
To: Tom Sightler <ttsig@tuxyturvy.com>
Cc: linux-kernel@vger.kernel.org
Subject: Re: Reiserfs, 3 Raid1 arrays, 2.4.1 machine locks up
Date: Tue, 20 Feb 2001 15:06:21 -0600	[thread overview]
Message-ID: <3A92DC4D.647EA0BB@pcxperience.com> (raw)
In-Reply-To: <3A91A6E7.1CB805C1@pcxperience.com> <96s93d$hh6$1@lennie.clouddancer.com> <20010220135326.013DF682A@mail.clouddancer.com> <3A92AA23.9A0BAC43@pcxperience.com> <20010220181849.F1C68682B@mail.clouddancer.com> <003701c09b75$59f56ff0$25040a0a@zeusinc.com> <3A92CBE6.A84B7ED3@pcxperience.com> <006b01c09b78$f8dd7e20$25040a0a@zeusinc.com>

Tom Sightler wrote:

> > > There seem to be several reports of reiserfs falling over when memory is
> > > low.  It seems to be undetermined if this problem is actually reiserfs
> or MM
> > > related, but there are other threads on this list regarding similar
> issues.
> > > This would explain why the same disk would work on a different machine
> with
> > > more memory.  Any chance you could add memory to the box temporarily
> just to
> > > see if it helps, this may help prove if this is the problem or not.
> > >
> >
> > Out of all the old 72 pin simms we have, we have it maxed out at 48 MB's.
> I'm
> > tempted to take the 2 drives out and put them in the k6-2, but that's too
> much
> > of a hassle.  I'm currently going to try 2.4.1-ac19 and see what happens.
> >
> > The machine does have 128MB of swap space working, and whenever I've
> checked
> > memory usage (while the system was still responding), it never went over a
> > couple megs of swap space used.
>
> Ah yes, but, from what I've read, the problem seems to occur when
> buffer/cache memory is low (<6MB), you could have tons of swap and still
> reach this level.
>
> Later,
> Tom

You were right!  I managed to find another 32MB of memory to bump it up to 64
MB total and it worked perfectly.  It appears that I had only about 4 MB of
buffer/cache in the 48 MB system and over 15MB in the 64 MB system.  I did my
install and switched back to the 48MB running normally and its working just
fine.

Thanks,


--
James A. Pattie
james@pcxperience.com

Linux  --  SysAdmin / Programmer
PC & Web Xperience, Inc.
http://www.pcxperience.com/




  reply	other threads:[~2001-02-20 21:08 UTC|newest]

Thread overview: 15+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2001-02-19 23:06 Reiserfs, 3 Raid1 arrays, 2.4.1 machine locks up James A. Pattie
     [not found] ` <96s93d$hh6$1@lennie.clouddancer.com>
     [not found]   ` <20010220135326.013DF682A@mail.clouddancer.com>
2001-02-20 17:32     ` James A. Pattie
2001-02-20 18:18       ` Colonel
2001-02-20 19:43         ` Tom Sightler
2001-02-20 19:56           ` James A. Pattie
2001-02-20 20:09             ` Tom Sightler
2001-02-20 21:06               ` James A. Pattie [this message]
2001-02-20 21:21           ` Colonel
2001-02-20 23:53             ` Roger Larsson
2001-02-21  3:49               ` Colonel
2001-02-21 14:45                 ` James A. Pattie
     [not found]                   ` <20010221161948.1FFD1682A@mail.clouddancer.com>
2001-02-21 16:43                     ` James A. Pattie
2001-02-21 20:26           ` Colonel
2001-02-22 20:36 ` Pavel Machek
2001-02-23 20:00 ` Jasmeet Sidhu

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=3A92DC4D.647EA0BB@pcxperience.com \
    --to=james@pcxperience.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=ttsig@tuxyturvy.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.