From: Joakim Tysseng <joakim.tysseng@opoint.com>
To: linux-kernel@vger.kernel.org
Subject: XFS lockup on 2.6.12-1.1376_FC3smp
Date: Thu, 15 Sep 2005 13:47:44 +0200 [thread overview]
Message-ID: <43295F60.6050303@opoint.com> (raw)
Hi,
I'm experiencing a serious problem with XFS on 2.6.12-1.1376_FC3smp
The filesystem locks up (no write possible, mysql won't shut down,
impossible to reboot machine from console) while running MySQL under a
high load. The only error messages I can find are:
thales kernel: allocation failed: out of vmalloc space - use
vmalloc=<size> to increase size.
thales kernel: XFS: possible memory allocation deadlock in kmem_alloc
(mode:0x250
I've tried increasing /proc/sys/vm/min_free_kbytes to 16386 without success.
Any ideas? Where should I start looking, what logs, programs/tests can i
run?
The problem does not appear immediately, the shortest time from reboot
to failure has been 4 hours.
Machine config:
Dell 6650 / 4 x P4 Xeon with 12GB ram.
1.5T SCSI disk array / PW220S / Perc 4/DC
running XFS on top of LVM.
--
Sincerely,
Joakim Tysseng
next reply other threads:[~2005-09-15 11:48 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2005-09-15 11:47 Joakim Tysseng [this message]
2005-09-17 5:26 ` XFS lockup on 2.6.12-1.1376_FC3smp Chris Wedgwood
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=43295F60.6050303@opoint.com \
--to=joakim.tysseng@opoint.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 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.