public inbox for linux-xfs@vger.kernel.org
 help / color / mirror / Atom feed
From: Martin Steigerwald <ms@teamix.de>
To: Eric Sandeen <sandeen@sandeen.net>
Cc: Timothy Shimmin <tes@sgi.com>, xfs@oss.sgi.com
Subject: Re: Is it possible the check an frozen XFS filesytem to avoid downtime
Date: Wed, 16 Jul 2008 09:53:56 +0200	[thread overview]
Message-ID: <200807160953.56503.ms@teamix.de> (raw)
In-Reply-To: <487CC1EB.6030100@sandeen.net>

Am Dienstag, 15. Juli 2008 17:27:39 schrieb Eric Sandeen:
> Martin Steigerwald wrote:
> > Okay... we recommended the customer to do it the safe way unmounting the
> > filesystem completely. He did and the filesystem appear to be intact
> > *phew*. XFS appeared to detect the in memory corruption early enough.
> >
> > Its a bit strange however, cause we now know that the server sports ECC
> > RAM. Well we will see what memtest86+ has to say about it.
>
> in-memory corruption could mean, but certainly does not absolutely mean,
> problematic memory.  It could be, and usually is, a plain ol' bug (in
> xfs or elsewhere).

Thanks. 

Yes, I thought about this, too. But then the machine ran over one year without 
any visible issues. And it happened only on one server, not on the other. It 
happened on the server that does NFS tough... could be an NFS related issue 
then. The other one does MySQL with the database stored on a XFS volume, too. 
But there haven't been any visible issues.

Well we will see whether it happens again on the server that has taken over 
and is now doing both MySQL and NFS. If it does, I think we will update to 
one of the lastest Debian Etch backport kernels (2.6.24 or even 2.6.25) on 
one of the servers and see whether that helps.

-- 
Martin Steigerwald - team(ix) GmbH - http://www.teamix.de
gpg: 19E3 8D42 896F D004 08AC A0CA 1E10 C593 0399 AE90

  reply	other threads:[~2008-07-16  7:53 UTC|newest]

Thread overview: 10+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2008-07-14 13:42 Is it possible the check an frozen XFS filesytem to avoid downtime Martin Steigerwald
2008-07-15  3:38 ` Timothy Shimmin
2008-07-15  7:44   ` Martin Steigerwald
2008-07-15 15:27     ` Eric Sandeen
2008-07-16  7:53       ` Martin Steigerwald [this message]
2008-10-27 16:57       ` Martin Steigerwald
2008-10-27 17:15         ` Eric Sandeen
2008-10-28  8:36           ` Martin Steigerwald
2008-07-16  8:55     ` Timothy Shimmin
2008-07-15  7:47   ` Martin Steigerwald

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=200807160953.56503.ms@teamix.de \
    --to=ms@teamix.de \
    --cc=sandeen@sandeen.net \
    --cc=tes@sgi.com \
    --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