From: Stan Hoeppner <stan@hardwarefreak.com>
To: xfs@oss.sgi.com
Subject: Re: possible xfs corruption
Date: Tue, 07 Dec 2010 12:15:54 -0600 [thread overview]
Message-ID: <4CFE79DA.9080400@hardwarefreak.com> (raw)
In-Reply-To: <30398538.post@talk.nabble.com>
blacknred put forth on 12/7/2010 11:30 AM:
>
> 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....
Out of the blue, one OP, with two Proliant servers having storage
problems, within hours of one another, the same day?
Long odds, that.
Did you walk a mile, flat footed, on deep shag carpet, while wearing a
wool sweater, in a room with zero humidity, then walk into the DC and
touch each of these servers, or something? ;)
--
Stan
_______________________________________________
xfs mailing list
xfs@oss.sgi.com
http://oss.sgi.com/mailman/listinfo/xfs
next prev parent reply other threads:[~2010-12-07 18:14 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
2010-12-07 18:15 ` Stan Hoeppner [this message]
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=4CFE79DA.9080400@hardwarefreak.com \
--to=stan@hardwarefreak.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