From: Emmanuel Florac <eflorac@intellique.com>
To: GuangYang <yguang11@outlook.com>
Cc: "xfs@oss.sgi.com" <xfs@oss.sgi.com>
Subject: Re: EIO and data corruption on XFS file system
Date: Thu, 6 Nov 2014 15:27:41 +0100 [thread overview]
Message-ID: <20141106152741.2655245d@harpe.intellique.com> (raw)
In-Reply-To: <BLU175-W376F83659C1C70DE51C3D9DF840@phx.gbl>
Le Thu, 6 Nov 2014 13:03:45 +0000
GuangYang <yguang11@outlook.com> écrivait:
> Hello,While working on the storage system, I got one question in
> terms of the XFS utilities to fix file system corruption. Basically,
> our storage system put 3 copies of data and the system would detect
> data inconsistency on regular basis, there are two patterns we
> observed so far: 1) the data is corrupted which result in an EIO, 2)
> data is still accessible but the content is changed. I am wondering
> the way to fix such issues from file system's perspective, do we
> expect hardware failure for both cases or some xfs repairing tools
> could help for such case?
XFS relies on the underlying hardware to maintain data integrity. The
latest XFS version comes with metadata checksums, which allows
correcting invalid data in filesystem structures, but not data.
Generally speaking, if the data is corrupted because of faulty hardware,
xfs_repair can't help.
regards,
--
------------------------------------------------------------------------
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
next prev parent reply other threads:[~2014-11-06 14:27 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-11-06 13:03 EIO and data corruption on XFS file system GuangYang
2014-11-06 14:27 ` Emmanuel Florac [this message]
2014-11-10 2:54 ` GuangYang
2014-11-06 17:55 ` Stan Hoeppner
2014-11-10 2:57 ` GuangYang
2014-11-10 14:54 ` Emmanuel Florac
2014-11-06 21:54 ` Dave Chinner
2014-11-10 2:59 ` GuangYang
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=20141106152741.2655245d@harpe.intellique.com \
--to=eflorac@intellique.com \
--cc=xfs@oss.sgi.com \
--cc=yguang11@outlook.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