From: Timothy Shimmin <tes@sgi.com>
To: mlueck@lueckdatasystems.com
Cc: linux-xfs@oss.sgi.com
Subject: Re: Bad day with xfsrestore, what went wrong?
Date: Tue, 28 Oct 2008 13:10:01 +1100 [thread overview]
Message-ID: <49067479.6070604@sgi.com> (raw)
In-Reply-To: <ge5kle$ueo$1@ger.gmane.org>
Hi Michael,
Michael Lueck wrote:
> xfsrestore -J -E -f /mnt/ext_backup/ldslnx01/20061220/data -s shares/data -i -v verbose /srv
> Bill Kendall wrote:
>
>> I tried to reproduce this using the command line you supplied, but
>> everything worked as expected for me.
>
> Glad to hear that. Seems my tried and true syntax _can_ still work.
>
>> Perhaps try it without the -i (so that only subtrees given with -s are
>> restored), just to rule out
>> the possibility that you inadvertently added all files to the restore
>> list.
>
> Enough putzing with a production server I think.
>
> It was odd that it only put back files present in that old backup set
> and did not overwrite everything... thankfully!
>
Maybe the -E option helped you out there.
-E Prevents xfsrestore from overwriting newer versions of files.
The inode modification time of the on-media file is com‐
pared to the inode modification time of corresponding file in the dest directory.
The file is restored only if the on-media version is newer than the version
in the dest directory. The inode modification time of a file can be displayed
with the ls -lc command.
--Tim
next prev parent reply other threads:[~2008-10-28 2:10 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-10-19 1:13 Bad day with xfsrestore, what went wrong? Michael Lueck
2008-10-27 2:22 ` Michael Lueck
2008-10-27 22:23 ` Bill Kendall
2008-10-27 23:59 ` Michael Lueck
2008-10-28 2:10 ` Timothy Shimmin [this message]
2008-10-28 2:16 ` Michael Lueck
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=49067479.6070604@sgi.com \
--to=tes@sgi.com \
--cc=linux-xfs@oss.sgi.com \
--cc=mlueck@lueckdatasystems.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.