From: David Chinner <dgc@sgi.com>
To: "Felix E. Klee" <felix.klee@inka.de>
Cc: Timothy Shimmin <tes@sgi.com>, xfs@oss.sgi.com
Subject: Re: Restoring damaged incremental XFS dump?
Date: Tue, 12 Feb 2008 23:24:46 +1100 [thread overview]
Message-ID: <20080212122446.GE155407@sgi.com> (raw)
In-Reply-To: <1202815035.5821.1236404891@webmail.messagingengine.com>
On Tue, Feb 12, 2008 at 12:17:15PM +0100, Felix E. Klee wrote:
> 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.
Use dm-snap to create a snapshot and do the backup from that.
Cheers,
Dave.
--
Dave Chinner
Principal Engineer
SGI Australian Software Group
prev parent reply other threads:[~2008-02-12 12:24 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
2008-02-12 12:24 ` David Chinner [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=20080212122446.GE155407@sgi.com \
--to=dgc@sgi.com \
--cc=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