From: blacknred <leo1783@hotmail.co.uk>
To: xfs@oss.sgi.com
Subject: Re: possible xfs corruption
Date: Tue, 7 Dec 2010 09:30:23 -0800 (PST) [thread overview]
Message-ID: <30398538.post@talk.nabble.com> (raw)
In-Reply-To: <20101207164227.152cef01@harpe.intellique.com>
It's all xfs..... and didn't see any I/O errors as well...except that dmesg
is flooded with similar traces to one i posted....
Emmanuel Florac wrote:
>
> 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
>
>
--
View this message in context: http://old.nabble.com/possible-xfs-corruption-tp30395558p30398538.html
Sent from the Xfs - General mailing list archive at Nabble.com.
_______________________________________________
xfs mailing list
xfs@oss.sgi.com
http://oss.sgi.com/mailman/listinfo/xfs
next prev parent reply other threads:[~2010-12-07 17:28 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
2010-12-07 17:30 ` blacknred [this message]
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=30398538.post@talk.nabble.com \
--to=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