public inbox for linux-xfs@vger.kernel.org
 help / color / mirror / Atom feed
From: David Chinner <dgc@sgi.com>
To: support@geoglobal.com
Cc: xfs@oss.sgi.com, vincent.roy@geoglobal.com
Subject: Re: Fwd: xfs_repair -n report
Date: Tue, 22 Apr 2008 08:31:14 +1000	[thread overview]
Message-ID: <20080421223114.GS108924158@sgi.com> (raw)
In-Reply-To: <200804211452.01772.support@geoglobal.com>

On Mon, Apr 21, 2008 at 02:52:01PM -0600, support@geoglobal.com wrote:
> Sorry, I truncated the original logfile of 128MB to a short version for 
> review. Again, all comments welcome.

Firstly, please post plain text attachments - that will cut down the
size of them as well...

> 
> Subject: xfs_repair -n report
> Date: Saturday 19 April 2008 23:22
> From: support@geoglobal.com
> To: xfs@oss.sgi.com, vincent.roy@geoglobal.com
> 
> RAID 5 - 4 disks on 9550 AMCC production machine / backup disk failed also
> verified without error - rebuilt after abrupt power shut down
> cannot mount - inconsistencies indicated - could not dump fs

Secondly, your raid has completely screwed the filesystem. I would
strongly suggest that you confirm that the rebuild of the RAID put
stuff back together properly (check things like the order of disks
in the stripe, etc). If it claims nothing is wrong, then it has been
lying to you.

I hope you have backups, because that's the only way you're going
to recover this mess.

Cheers,

Dave.
-- 
Dave Chinner
Principal Engineer
SGI Australian Software Group

  reply	other threads:[~2008-04-21 22:31 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2008-04-21 20:52 Fwd: xfs_repair -n report support
2008-04-21 22:31 ` David Chinner [this message]
     [not found]   ` <003701c8a41b$91b416b0$2f0a0a0a@geoglobal.ca>
2008-04-22  1:52     ` Vincent Roy
  -- strict thread matches above, loose matches on Subject: below --
2008-04-22 22:56 support

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=20080421223114.GS108924158@sgi.com \
    --to=dgc@sgi.com \
    --cc=support@geoglobal.com \
    --cc=vincent.roy@geoglobal.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