From: Bill Kendall <wkendall@sgi.com>
To: Rick Meertens <rick@datux.nl>
Cc: xfs@oss.sgi.com
Subject: Re: consistency checks
Date: Wed, 25 Nov 2009 09:48:12 -0600 [thread overview]
Message-ID: <4B0D51BC.5020806@sgi.com> (raw)
In-Reply-To: <vmime.4b0c0e17.1df4.5b5ba8b45ea0c16c@mail.datux.nl>
Rick Meertens wrote:
> Does the xfs backup tools contain any backup media consistency checks? I
> want to verify if the old backup on a tape is corrupt, with a checksum orso.
>
>
>
> I have seen that the xfsdump inventory can be checked on consistency,
> but nothing found for the tapes
Not really -- unfortunately most of the structures and data written
by xfsdump are not checksummed.
The closest thing is to use xfrestore -t. This will read the entire
dump, listing all of the files it contains. So you'll at least know
whether or not there are unreadable blocks on the media, and whether
the structure of the dump is okay, but not whether your file data is
consistent.
Bill
_______________________________________________
xfs mailing list
xfs@oss.sgi.com
http://oss.sgi.com/mailman/listinfo/xfs
prev parent reply other threads:[~2009-11-25 15:47 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-11-24 16:47 consistency checks Rick Meertens
2009-11-25 15:48 ` Bill Kendall [this message]
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=4B0D51BC.5020806@sgi.com \
--to=wkendall@sgi.com \
--cc=rick@datux.nl \
--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