public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: Samuel Flory <sflory@valinux.com>
To: Tigran Aivazian <tigran@veritas.com>
Cc: linux-kernel@vger.kernel.org
Subject: Re: mke2fs and kernel VM issues
Date: Fri, 16 Feb 2001 11:01:24 -0800	[thread overview]
Message-ID: <3A8D7904.94C477F2@valinux.com> (raw)
In-Reply-To: <Pine.LNX.4.21.0102161058580.2099-100000@penguin.homenet>

Tigran Aivazian wrote:
> 
> On Thu, 15 Feb 2001, Samuel Flory wrote:
> 
> >   What is believed to be the current status of the typical mke2fs
> > crashes/hangs due to vm issues?  I can reliably reproduce the issue on a
> > heavily modifed VA kernel based on 2.2.18.  Is there a kernel which is
> > believed to be a known good kernel?  (both 2.2.x and 2.4.x)
> 
> I can mke2fs (successfully) on a 270G block device. Yes, of course, I also
> get various page allocation failures while this happens but they are not
> deadly, i.e. the thing (our volume manager) just retries until it works
> and after a while I have a valid (and a very big) ext2 filesystem with 0
> processes killed.
> 
> The kernel I use is 2.4.2-pre3. The machine has 6G RAM with the 3G given
> to kernel virtual. The amount of swap is massive (2G) but it is never
> used.

  I've never been able reliably reproduce any sort of mke2fs hang on
systems with more than 512M of RAM.  It would be interesting to know if
other people are seeing this under SW-RAID, and other controllers. 
(Currently everyone in direct contact with me uses a Mylex controller.) 
The key seems to be 512 or smaller amounts of RAM, and a 80G or larger
logical drive.

-- 
Solving people's computer problems always
requires more hardware be given to you.
(The Second Rule of Hardware Acquisition)
Samuel J. Flory  <sam@valinux.com>

  reply	other threads:[~2001-02-16 19:02 UTC|newest]

Thread overview: 12+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2001-02-16  0:38 [OTP] SMP board recommendations? David D.W. Downey
2001-02-16  1:43 ` mke2fs and kernel VM issues Samuel Flory
2001-02-16  9:48   ` Alan Cox
2001-02-16 12:44     ` tytso
2001-02-16 12:49       ` Alan Cox
2001-02-19 15:06       ` Andrea Arcangeli
2001-02-16 19:01     ` Samuel Flory
2001-02-16 11:05   ` Tigran Aivazian
2001-02-16 19:01     ` Samuel Flory [this message]
2001-02-16  5:03 ` [OTP] SMP board recommendations? David D.W. Downey
2001-02-16  6:27   ` Andre Hedrick
2001-02-16 10:49 ` Roeland Th. Jansen

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=3A8D7904.94C477F2@valinux.com \
    --to=sflory@valinux.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=tigran@veritas.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