From: Samuel Flory <sflory@valinux.com>
To: linux-kernel@vger.kernel.org
Cc: "tytso@valinux.com" <tytso@valinux.com>
Subject: mke2fs and kernel VM issues
Date: Thu, 15 Feb 2001 17:43:21 -0800 [thread overview]
Message-ID: <3A8C85B9.610D0C06@valinux.com> (raw)
In-Reply-To: <Pine.LNX.4.30.0102151634380.16783-100000@ns-01.hislinuxbox.com>
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)
Failure pattern:
System:
mylex raid 5 array 8 x 9G drives (not really all that big)
>=512M of RAM (1G of RAM works)
no swap (Not sure if this makes a difference.)
The system is attempting to create a single partition containing the
most of the entire RAID array.
errors:
buffy: Installing with LIVE AMMO
Creating partitions...
Initializing filesystems...
Out of Memory: Killed process 106 (portmap), saved process 2165
(mke2fs).<3>Out
of Memory: Killed process 2123 (buffy), saved process 2165
(mke2fs).willow: LOAD
FAILED
<3>Out of Memory: Killed process 195 (sisyphus_upload), saved process
2165 (mke2
fs).<3>Out of Memory: Killed process 2165 (mke2fs).
(Note that most of the above proccesses were dialog interfaces waiting
for user input or perl scripts waiting for mke2fs or buffy to exit.)
PS- Conversations with various VA empolyees indicates that others within
VA, and at least one vendor are seeing hangs while creating really large
filesystems on RAID arrays. (mostly 1/4 TB or larger) These issues
appear to come and go, and are endemic to the 2.2.x kernel line. Both
lnz and tytso seem to believe the issues to be vm entirely related.
--
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>
next prev parent reply other threads:[~2001-02-16 1:43 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 ` Samuel Flory [this message]
2001-02-16 9:48 ` mke2fs and kernel VM issues 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
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=3A8C85B9.610D0C06@valinux.com \
--to=sflory@valinux.com \
--cc=linux-kernel@vger.kernel.org \
--cc=tytso@valinux.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.