From: daniel+devel.linux.lkml@flexserv.de
To: linux-kernel@vger.kernel.org
Subject: Re: Bug: XFS internal error XFS_WANT_CORRUPTED_RETURN
Date: Fri, 16 Jun 2006 23:38:05 +0200 [thread overview]
Message-ID: <87irn0zsqq.fsf@xserver.flexserv.de> (raw)
In-Reply-To: <200606161835.26428.s0348365@sms.ed.ac.uk> (Alistair John Strachan's message of "Fri, 16 Jun 2006 18:35:26 +0100")
[-- Attachment #1: Type: text/plain, Size: 547 bytes --]
Alistair John Strachan <s0348365@sms.ed.ac.uk> writes:
> On Friday 16 June 2006 15:09, daniel+devel.linux.lkml@flexserv.de wrote:
>> What additional informatiuon can i get you?
On a tmpfs or ext2/3 i dont get it.
> Just make sure you've run memtest for at least a couple passes to eliminate
> bad RAM. This could still easily be an XFS bug, but it's worth checking.
Its an full equiped E420R 4*450Mhz 4GB RAM.
I dont know a memtesttool for sparcs.
If you know one please drop me a line.
every test from obp runs fine.
Daniel
[-- Attachment #2: Type: application/pgp-signature, Size: 188 bytes --]
next prev parent reply other threads:[~2006-06-16 21:38 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-06-16 14:09 Bug: XFS internal error XFS_WANT_CORRUPTED_RETURN daniel+devel.linux.lkml
2006-06-16 17:35 ` Alistair John Strachan
2006-06-16 21:38 ` daniel+devel.linux.lkml [this message]
2006-06-16 22:07 ` Jan Engelhardt
2006-06-16 22:11 ` Justin Piszcz
2006-06-17 9:25 ` Jan Engelhardt
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=87irn0zsqq.fsf@xserver.flexserv.de \
--to=daniel+devel.linux.lkml@flexserv.de \
--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.