All of lore.kernel.org
 help / color / mirror / Atom feed
From: Ben Myers <bpm@sgi.com>
To: Patrick Shirkey <pshirkey@boosthardware.com>
Cc: xfs@oss.sgi.com
Subject: Re: file corruption issue
Date: Fri, 11 May 2012 11:50:12 -0500	[thread overview]
Message-ID: <20120511165012.GC16099@sgi.com> (raw)
In-Reply-To: <51509.110.174.53.110.1336699622.squirrel@boosthardware.com>

On Fri, May 11, 2012 at 03:27:02AM +0200, Patrick Shirkey wrote:
> I have some HP machines running centos:
> 
> kernel 2.6.32-042stab049.6
> AMD Opteron(tm) Processor 6180 SE
> RAM:   528 GB
> RAID bus controller: Hewlett-Packard Company Smart Array G6 controllers
> 
> We have experienced some kernel crashes due to a kernel bug with
> interleaving ram on this hardware which require hard reset of the
> machines.
> 
> After reboot we are finding that there is severe file corruption on the
> xfs file system where TBs of readonly databases are getting partially or
> fully truncated.
> 
> Has anyone come across this or similar?

This rings a bell for me but I can't be certain.  Could you provide a metadump?

-Ben

_______________________________________________
xfs mailing list
xfs@oss.sgi.com
http://oss.sgi.com/mailman/listinfo/xfs

  reply	other threads:[~2012-05-11 16:46 UTC|newest]

Thread overview: 10+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2012-05-11  1:27 file corruption issue Patrick Shirkey
2012-05-11 16:50 ` Ben Myers [this message]
2012-05-14  1:45   ` Patrick Shirkey
2012-05-14 14:29     ` Ben Myers
2012-05-15  0:58       ` Patrick Shirkey
2012-05-15 15:13         ` Ben Myers
2012-05-16  2:30           ` Patrick Shirkey
2012-05-24 15:33             ` Ben Myers
2012-05-24 21:46               ` Patrick Shirkey
     [not found]         ` <20120601203451.32ae2ed5@asix.localdomain>
2012-06-01 12:38           ` Igor M Podlesny

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=20120511165012.GC16099@sgi.com \
    --to=bpm@sgi.com \
    --cc=pshirkey@boosthardware.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 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.