From: "Patrick Shirkey" <pshirkey@boosthardware.com>
To: xfs@oss.sgi.com
Subject: Re: file corruption issue
Date: Tue, 15 May 2012 02:58:42 +0200 (CEST) [thread overview]
Message-ID: <64776.110.174.53.110.1337043522.squirrel@boosthardware.com> (raw)
In-Reply-To: <20120514142948.GS3963@sgi.com>
On Mon, May 14, 2012 4:29 pm, Ben Myers wrote:
> Hey Patrick,
>
> On Mon, May 14, 2012 at 03:45:06AM +0200, Patrick Shirkey wrote:
>>
>> On Fri, May 11, 2012 6:50 pm, Ben Myers wrote:
>> > 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?
>> >
>>
>> The machines are live so we have already restored the data several
>> times.
>> Will a metadump from the existing file system be useful or do you need
>> it
>> post crash?
>
> Well... one of each would be best. It might be helpful to compare the
> block
> map from before the crash with the block map after the crash for one of
> the
> read-only corrupted databases.
>
Unfortunately I cannot unmount the partition/s to run xfs_metadump because
they are in use.
I have found some files that were truncated on a recent crash. Is there
any tool I can run on those files to get info that might be useful?
--
Patrick Shirkey
Boost Hardware Ltd
_______________________________________________
xfs mailing list
xfs@oss.sgi.com
http://oss.sgi.com/mailman/listinfo/xfs
next prev parent reply other threads:[~2012-05-15 0:58 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
2012-05-14 1:45 ` Patrick Shirkey
2012-05-14 14:29 ` Ben Myers
2012-05-15 0:58 ` Patrick Shirkey [this message]
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=64776.110.174.53.110.1337043522.squirrel@boosthardware.com \
--to=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.