From: Stan Hoeppner <stan@hardwarefreak.com>
To: Rotem Ben Arye <rotem.benarye@gmail.com>, support@sgi.com
Cc: xfs@oss.sgi.com
Subject: Re: XFS File System Monitor
Date: Thu, 02 Jan 2014 09:07:01 -0600 [thread overview]
Message-ID: <52C58095.70408@hardwarefreak.com> (raw)
In-Reply-To: <CA+apj_hV4HvZxfASF7JJ1k6mmvio3cRWAHj-S1V=Vm8X_RWA=Q@mail.gmail.com>
On 1/2/2014 6:16 AM, Rotem Ben Arye wrote:
> Hi, SGI Support Team.
> My Name is Rotem , I am a Linux/Unix System Administrator in web company at
> Israel.
> I have a question I want to appeal to you to get some advice.
>
> In the last weekend we had crisis in one of the Production server in
> the comany ,the problem was defined by the Integrators as "xfs file system
> corrupted"
> My question is , what are the open source tools , that we can use on
> runtime at production environment , to monitor and sample to get indication
> on mount XFS ,
> That something is not living well, and can lead to problem.
>
> We are working in a Linux environment on CentOS distributions server.
So in a nutshell you're looking for a monitor application that will in
essence give you a green, yellow, or red light informing you of the
filesystem's health. Or some kind of SNMP logging that suggests a
corruption is imminent.
There is no such tool, and never will be. Nearly all XFS corruption
events are caused by either software bugs in the XFS code or elsewhere
in the Linux kernel, transient or permanent hardware failures, or power
failures, at some layer in the storage stack. It is not feasible to
predict such events.
When an XFS corruption occurs, one should report all related log
information and errors to this list so that the problem may be analyzed
and the root cause identified. Then the proper corrective action can be
identified and implemented to fix the problem and hopefully prevent it
from reoccurring.
--
Stan
_______________________________________________
xfs mailing list
xfs@oss.sgi.com
http://oss.sgi.com/mailman/listinfo/xfs
next prev parent reply other threads:[~2014-01-02 15:07 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-01-02 12:16 XFS File System Monitor Rotem Ben Arye
2014-01-02 15:07 ` Stan Hoeppner [this message]
[not found] ` <CA+apj_iOy2dqyPGunKe91WLCqy71uE1uq2HZQ_v=+QHewCymeA@mail.gmail.com>
2014-01-04 15:45 ` Stan Hoeppner
-- strict thread matches above, loose matches on Subject: below --
2014-01-02 13:04 support
2014-01-02 13:20 ` Rotem Ben Arye
2014-01-02 13:27 ` Emmanuel Florac
2014-01-03 18:24 ` Eric Sandeen
2014-01-04 7:27 ` Rotem Ben Arye
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=52C58095.70408@hardwarefreak.com \
--to=stan@hardwarefreak.com \
--cc=rotem.benarye@gmail.com \
--cc=support@sgi.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;
as well as URLs for NNTP newsgroup(s).