From: Eric Sandeen <sandeen@sandeen.net>
To: "Zak, Semion" <SZak@nds.com>
Cc: xfs@oss.sgi.com
Subject: Re: XFS Resiliency to the disk errors.
Date: Thu, 05 Apr 2007 11:06:30 -0500 [thread overview]
Message-ID: <46151E86.2080704@sandeen.net> (raw)
In-Reply-To: <A63C579E7F04E74588517328EF5A385E02076A9A@ILEX5.IL.NDS.COM>
Zak, Semion wrote:
> Hi,
>
> We are studying possibility to use XFS with cheap (not too reliable)
> discs, so we have some questions:
>
> What in XFS is done to survive the disk errors (bad sectors)?
> I know about superblock duplication in every AG. What else?
>
> What is XFS behavior in case of the disk errors (panic/no mount/partial
> data access)?
generally metadata IO errors or bad magic found in metadata will shut
down the filesystem gracefully if it can.
IO errors on data will just be IO errors.
> What could be done to restore?
xfsdump/xfsrestore I suppose
> If zero bad sector/dump to other device/format/restore will help?
Well, you can't make data out of nothing.
you could dd off the junk drive, zeroing out unreadable sectors, point
xfs_repair at it and hope for the best. Which, depending on the
problem, could wind up not being very good.
If you want to know how to recover from disaster, it sounds like perhaps
your data is important enough that you should not plan for failure, but
rather find a way to avoid it?
Seems to me the only way I'd want to put drives which are expected to
fail regularly into a product is if the recovery method of "replace the
disk and re-image the appliance" was acceptable, but that's just me. :)
-Eric
next prev parent reply other threads:[~2007-04-05 16:06 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-04-05 8:08 XFS Resiliency to the disk errors Zak, Semion
2007-04-05 16:06 ` Eric Sandeen [this message]
2007-04-10 6:49 ` Zak, Semion
2007-04-06 18:49 ` Peter Grandi
2007-04-07 20:47 ` Martin Steigerwald
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=46151E86.2080704@sandeen.net \
--to=sandeen@sandeen.net \
--cc=SZak@nds.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