From: Juergen Sauer <jojo@automatix.de>
To: Pascal Haakmat <a.haakmat@chello.nl>, linux-kernel@vger.kernel.org
Subject: Re: XFS Oopses with 2.4.5 and 2.4.14?
Date: Wed, 28 Nov 2001 16:29:07 +0100 [thread overview]
Message-ID: <E1696e6-0004nn-00@s.automatix.de> (raw)
In-Reply-To: <000701c177e6$7317af40$ea9133d5@groni1.gr.nl.home.com> <20011128155716.A7302@awacs.dhs.org>
In-Reply-To: <20011128155716.A7302@awacs.dhs.org>
Am Mittwoch, 28. November 2001 15:57 schrieb Pascal Haakmat:
> Given the following Oopses, is it wise to continue running the XFS
> filesystem, or might there be some other underlying problem that is
> causing these Oopses?
>
> Kernel 2.4.5 + XFS 1.0.1:
>
> Nov 25 07:28:23 awacs kernel: Unable to handle kernel paging request at
[...]
I had these problems in the past with a inconsitent XFS Filesystem, I'd
recommend to run xfs_repair on your XFS filesystems, using a external
Rescue CD - bootdisk/bootCD. If you have none handy, drop me a mail.
The fs-troubles on my server was arising using a Highend-Caching
controller (ICP-Vortex), and not flushing the cache before power down.
After several power downs the XFS had headaches, and I had such
kernel-oops.
mfG
Jojo
--
Jürgen Sauer - AutomatiX GmbH, +49-4209-4699, jojo@automatix.de **
** Das Linux Systemhaus - Service - Support - Server - Lösungen **
http://www.automatix.de to Mail me: remove: -not-for-spawm- **
next prev parent reply other threads:[~2001-11-28 15:37 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <000701c177e6$7317af40$ea9133d5@groni1.gr.nl.home.com>
2001-11-28 14:57 ` XFS Oopses with 2.4.5 and 2.4.14? Pascal Haakmat
2001-11-28 15:29 ` Juergen Sauer [this message]
2001-11-28 16:05 ` Peter Wächtler
2001-11-28 15:29 Elgar, Jeremy
[not found] <fa.ih0gaiv.iio4rf@ifi.uio.no>
[not found] ` <fa.ge28glv.66a6b8@ifi.uio.no>
2001-11-28 15:48 ` Eric Sandeen
2001-11-28 16:31 ` Pascal Haakmat
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=E1696e6-0004nn-00@s.automatix.de \
--to=jojo@automatix.de \
--cc=a.haakmat@chello.nl \
--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