linux-kernel.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Paul Buder <paulb@aracnet.com>
To: <linux-kernel@vger.kernel.org>
Subject: Large ramdisk crashes system
Date: Thu, 7 Jun 2001 16:09:01 -0700 (PDT)	[thread overview]
Message-ID: <Pine.LNX.4.33.0106071607180.3940-100000@shell1.aracnet.com> (raw)

I am trying to create a system which boots off of a cd and has no hard
disks.  So it needs ramdisks.  But I haven't had much luck creating
large ones.

I tried on two different boxes.  In both cases the kernel is 2.4.5 with
'Simple RAM-based file system support' turned on.

One box is a dual Pentium 750 with a gig of ram in it.  I had the
kernel 'Default RAM disk size' set to 800000 for this box.  I issued
the following commands.

mkfs /dev/ram0 400000
mount /dev/ram0 /mnt
dd if=/dev/zero of=/mnt/junk bs=1024 count=500000

This is fine, dd creates a 400 meg file, reports there isn't enough
space and exits.  But if I change the first line to

mkfs /dev/ram0 500000

I'm essentially crashed.  I can ping the box and switch between virtual
terminals but that's it.  Any program that was running on the other
virtual terminals is frozen (as in top, tail, login).  The dd is frozen
and can't be control-c'd.  so I can't do anything other than powercycle.
I should have at least 400 megs of ram left for the system so I don't
get it.

I tried the same thing on a 128 meg box.  The results were similar.  A 40
meg ram disk worked.  A 60 meg ram disk crashed the box.  The numbers
seem a little odd since in both cases the magic threshold seems to be
roughly 40% of ram.

I get no messages in the system logfiles nor an oops on the screen.

Any ideas?


             reply	other threads:[~2001-06-07 23:09 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2001-06-07 23:09 Paul Buder [this message]
2001-06-07 21:48 ` Large ramdisk crashes system Marcelo Tosatti
2001-06-08 19:32   ` Paul Buder
2001-06-07 23:35 ` David Woodhouse
2001-06-08 19:33   ` Paul Buder

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=Pine.LNX.4.33.0106071607180.3940-100000@shell1.aracnet.com \
    --to=paulb@aracnet.com \
    --cc=linux-kernel@vger.kernel.org \
    /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;
as well as URLs for NNTP newsgroup(s).