From: Martin Steigerwald <Martin@lichtvoll.de>
To: xfs@oss.sgi.com
Subject: Re: xfs in memory corruption
Date: Sat, 19 Dec 2009 11:50:09 +0100 [thread overview]
Message-ID: <200912191150.10149.Martin@lichtvoll.de> (raw)
In-Reply-To: <C751BC0C.A22%bchang@greenplum.com>
Am Samstag 19 Dezember 2009 schrieb Brady Chang:
> Hi
Hi Brady,
> all, got the following error on one of our test machines. SLES10 SP2
> with stock kernel
>
> I've not had the chance to scrutinize complete /var/log/messages for
> additional helpful info. Any advanced help is appreciated.
Thats likely 2.6.16.something. I strongly advise to upgrade the kernel.
Quite some XFS issues have been already fixed since then.
If you can't upgrade your kernel, I advise to contact Novell / SUSE
support and they whether they can backport a fix for this to their ancient
kernel.
Ciao,
--
Martin 'Helios' Steigerwald - http://www.Lichtvoll.de
GPG: 03B0 0D6C 0040 0710 4AFA B82F 991B EAAC A599 84C7
_______________________________________________
xfs mailing list
xfs@oss.sgi.com
http://oss.sgi.com/mailman/listinfo/xfs
prev parent reply other threads:[~2009-12-19 10:49 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-12-19 7:09 xfs in memory corruption Brady Chang
2009-12-19 10:50 ` Martin Steigerwald [this message]
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=200912191150.10149.Martin@lichtvoll.de \
--to=martin@lichtvoll.de \
--cc=xfs@oss.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox