public inbox for linux-xfs@vger.kernel.org
 help / color / mirror / Atom feed
From: Emmanuel Florac <eflorac@intellique.com>
To: blacknred <leo1783@hotmail.co.uk>
Cc: xfs@oss.sgi.com
Subject: Re: possible xfs corruption
Date: Tue, 7 Dec 2010 16:42:27 +0100	[thread overview]
Message-ID: <20101207164227.152cef01@harpe.intellique.com> (raw)
In-Reply-To: <30397173.post@talk.nabble.com>

Le Tue, 7 Dec 2010 07:11:04 -0800 (PST)
blacknred <leo1783@hotmail.co.uk> écrivait:

> Yes, It's a Smart Array in HP Proliant Server.
> No power failure, just upgraded the controller firmware and rebooted
> the server.....
> 

Hu oh, that stinks. Nothing in the firmware release notes? Do you have
any other filesystem on this array? 

First you could try to backup the filesystem metadata using

xfs_metadump -o -w /dev/DEVICE outfile.meta

It can be useful later in case things turn bad.
Does it output any errors? IO errors particularly ?

-- 
------------------------------------------------------------------------
Emmanuel Florac     |   Direction technique
                    |   Intellique
                    |	<eflorac@intellique.com>
                    |   +33 1 78 94 84 02
------------------------------------------------------------------------

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

  reply	other threads:[~2010-12-07 15:40 UTC|newest]

Thread overview: 9+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2010-12-07 11:49 possible xfs corruption blacknred
2010-12-07 14:10 ` Emmanuel Florac
2010-12-07 15:11   ` blacknred
2010-12-07 15:42     ` Emmanuel Florac [this message]
2010-12-07 17:30       ` blacknred
2010-12-07 18:15         ` Stan Hoeppner
2010-12-07 19:32     ` Michael Monnerie
2010-12-07 22:10 ` Dave Chinner
2010-12-09  3:44   ` Eric Sandeen

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=20101207164227.152cef01@harpe.intellique.com \
    --to=eflorac@intellique.com \
    --cc=leo1783@hotmail.co.uk \
    --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