From: Bill Kendall <wkendall@sgi.com>
To: Christoph Hellwig <hch@infradead.org>
Cc: xfs@oss.sgi.com
Subject: Re: [PATCH] xfsdump: incremental dump directory selection
Date: Fri, 28 Oct 2011 08:32:30 -0500 [thread overview]
Message-ID: <4EAAAEEE.5030600@sgi.com> (raw)
In-Reply-To: <20111028093752.GB23069@infradead.org>
Christoph Hellwig wrote:
> On Fri, Oct 21, 2011 at 11:35:33AM -0500, Bill Kendall wrote:
>> When doing incremental backups, xfsdump does a recursive scan through
>> the filesystems to determine the proper set of unchanged directories
>> to include in the dump in order to make the dump self-contained
>> (allowing files to be restored from this dump without applying the
>> base dumps first).
>>
>> For high-inode count filesystems, the recursive scan may consume a
>> significant portion of the backup time. This patch adds a -D option
>> which causes xfsdump to skip the recursive scan. Unchanged directories
>> will not be dumped, so the base dump(s) will have to be loaded prior
>> to restoring files from the dump. When restoring files from such a
>> dump, a message is issued to alert the user that files may end up in
>> the orphanage if the base dump(s) has not been applied.
>
> Any chance you could submit some xfstests coverage for this feature?
Sure, will do.
Bill
_______________________________________________
xfs mailing list
xfs@oss.sgi.com
http://oss.sgi.com/mailman/listinfo/xfs
prev parent reply other threads:[~2011-10-28 13:32 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-10-21 16:35 [PATCH] xfsdump: incremental dump directory selection Bill Kendall
2011-10-28 9:37 ` Christoph Hellwig
2011-10-28 13:32 ` 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=4EAAAEEE.5030600@sgi.com \
--to=wkendall@sgi.com \
--cc=hch@infradead.org \
--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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.