public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: Colonel <klink@clouddancer.com>
To: ttsig@tuxyturvy.com
Cc: james@pcxperience.com, linux-kernel@vger.kernel.org
Subject: Re: Reiserfs, 3 Raid1 arrays, 2.4.1 machine locks up
Date: Wed, 21 Feb 2001 12:26:02 -0800 (PST)	[thread overview]
Message-ID: <20010221202602.CC2E5682A@mail.clouddancer.com> (raw)
In-Reply-To: <003701c09b75$59f56ff0$25040a0a@zeusinc.com> (ttsig@tuxyturvy.com)
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>

   From: "Tom Sightler" <ttsig@tuxyturvy.com>
   Cc: <linux-kernel@vger.kernel.org>
   Date: Tue, 20 Feb 2001 14:43:07 -0500
   Content-Type: text/plain;
	   charset="iso-8859-1"

   >    > >I'm building a firewall on a P133 with 48 MB of memory using RH 7.0,
   >    > >latest updates, etc. and kernel 2.4.1.
   >    > >I've built a customized install of RH (~200MB)  which I untar onto
   the
   >    > >system after building my raid arrays, etc. via a Rescue CD which I
   >    > >created using Timo's Rescue CD project.  The booting kernel is
   >    > >2.4.1-ac10, no networking, raid compiled in but raid1 as a module
   >    >
   >    > Hmm, raid as a module was always a Bad Idea(tm) in the 2.2 "alpha"
   >    > raid (which was misnamed and is 2.4 raid).  I suggest you change that
   >    > and update, as I had no problems with 2.4.2-pre2/3, nor have any been
   >    > posted to the raid list.
   >
   >    I just tried with 2.4.1-ac14, raid and raid1 compiled in and it did the
   >    same thing.  I'm going to try to compile reiserfs in (if I have enough
   room
   >    to still fit the kernel on the floppy with it's initial ramdisk, etc.)
   and
   >    see what that does.

   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.


If you caught the end of the thread, james (the initial poster) added
memory, had no problems, removed the extra memory and still had no
problems.  His spare memory is greater than my memory total.  I too
cannot repeat the freeze.  It makes me wonder if there is some
parameter updating in the kernel somehow.


  parent reply	other threads:[~2001-02-21 20:26 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
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 [this message]
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=20010221202602.CC2E5682A@mail.clouddancer.com \
    --to=klink@clouddancer.com \
    --cc=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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox