From: Pascal Haakmat <a.haakmat@chello.nl>
To: Eric Sandeen <sandeen@sgi.com>, linux-kernel@vger.kernel.org
Subject: Re: XFS Oopses with 2.4.5 and 2.4.14?
Date: Wed, 28 Nov 2001 17:31:11 +0100 [thread overview]
Message-ID: <20011128173111.A8093@awacs.dhs.org> (raw)
In-Reply-To: <fa.ih0gaiv.iio4rf@ifi.uio.no> <fa.ge28glv.66a6b8@ifi.uio.no> <200111281548.fASFmlI01384@mail.swdata.com>
In-Reply-To: <200111281548.fASFmlI01384@mail.swdata.com>; from sandeen@sgi.com on Wed, Nov 28, 2001 at 09:48:47AM -0600
28/11/01 09:48, Eric Sandeen wrote:
> Hi Pascal -
>
> Did you compile these kernels yourself, and if so, what compiler did you
> use?
Yes:
Linux version 2.4.5-xfs-1.0.1 (root@awacs.dhs.org) (gcc version egcs-2.91.66
19990314/Linux (egcs-1.1.2 release)) #10 SMP Fri Sep 21 18:34:40 CEST 2001
Linux version 2.4.14-xfs-1.0.2 (root@awacs.dhs.org) (gcc version 2.96
20000731 (Red Hat Linux 7.1 2.96-98)) #2 SMP Sun Nov 25 08:15:50 CET 2001
> Can you reproduce this reliably?
No, that is to say, I haven't tried.
Somebody else has suggested FS corruption as the cause of these Oopses. That
might very well be the case. On multiple occassions (perhaps coinciding with
the Oopses, sorry I can't be more specific), my system has hung when trying
to write to a file, and I would be left with files looking somewhat like
this (from memory):
$ ls -lhsa spook.wav
0 -rw-r--r-- 1 p p 165k Nov 25 09:04 spook.wav
Up until now I just rm'd these files and continued, but I suppose I can try
an xfs_repair from the boot CD.
> I'd be happy to help with debugging this if you'd like, you might also
> take this over to linux-xfs@oss.sgi.com.
Thanks.
next prev parent reply other threads:[~2001-11-28 16:31 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <fa.ih0gaiv.iio4rf@ifi.uio.no>
[not found] ` <fa.ge28glv.66a6b8@ifi.uio.no>
2001-11-28 15:48 ` XFS Oopses with 2.4.5 and 2.4.14? Eric Sandeen
2001-11-28 16:31 ` Pascal Haakmat [this message]
2001-11-28 15:29 Elgar, Jeremy
[not found] <000701c177e6$7317af40$ea9133d5@groni1.gr.nl.home.com>
2001-11-28 14:57 ` Pascal Haakmat
2001-11-28 15:29 ` Juergen Sauer
2001-11-28 16:05 ` Peter Wächtler
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=20011128173111.A8093@awacs.dhs.org \
--to=a.haakmat@chello.nl \
--cc=linux-kernel@vger.kernel.org \
--cc=sandeen@sgi.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.