public inbox for linux-xfs@vger.kernel.org
 help / color / mirror / Atom feed
From: "Felix E. Klee" <felix.klee@inka.de>
To: Timothy Shimmin <tes@sgi.com>
Cc: xfs@oss.sgi.com
Subject: Re: Restoring damaged incremental XFS dump?
Date: Tue, 12 Feb 2008 12:17:15 +0100	[thread overview]
Message-ID: <1202815035.5821.1236404891@webmail.messagingengine.com> (raw)
In-Reply-To: <47B0E26D.7070807@sgi.com>

On Tue, 12 Feb 2008 11:03:57 +1100, "Timothy Shimmin"
<tes@sgi.com> said:
> I'm not sure what you mean by "true snapshots". I wouldn't really
> call it snapshots as in what you could get if you froze the
> filesystem etc..

Oh, it does not freeze the filesystem - what a pity.  I recall someone
telling me that it does.  Seems like that was bad information or my
memory is failing on me.

> > So, what happens when the level 0 dump created with xfsdump becomes
> > damaged.  Will I still be able to recover some files?  What about
> > files from >0 dumps?
>
> Yes you will still be able to restore stuff. However, it is in its own
> format so only xfsrestore will be able to do your restoring. Dumps are
> separated into what it calls media files which are meant to be self
> containing. So damage to 1 theoretically shouldn't prevent restoring
> from another media file. Multiple media files are normally only used
> for tape (only 1 used for a dump to a file). And an incremental dump
> should also be able to be restored in isolation and there are some QA
> tests (in xfs-cmds/xfstests) that test this.

Thanks!

Felix

-- 
Dipl.-Phys. Felix E. Klee
Naunynstr. 2, 76530 Baden-Baden, Germany
Tel.: +49 7221 396961, Fax: +49 7221 396960, Mobile: +49 174 1386060
http://www.linkedin.com/in/feklee

  reply	other threads:[~2008-02-12 11:17 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2008-02-11 22:39 Restoring damaged incremental XFS dump? Felix E. Klee
2008-02-12  0:03 ` Timothy Shimmin
2008-02-12 11:17   ` Felix E. Klee [this message]
2008-02-12 12:24     ` David Chinner

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=1202815035.5821.1236404891@webmail.messagingengine.com \
    --to=felix.klee@inka.de \
    --cc=tes@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