public inbox for linux-xfs@vger.kernel.org
 help / color / mirror / Atom feed
From: Bill Kendall <wkendall@sgi.com>
To: mlueck@lueckdatasystems.com
Cc: linux-xfs@oss.sgi.com
Subject: Re: Bad day with xfsrestore, what went wrong?
Date: Mon, 27 Oct 2008 17:23:49 -0500	[thread overview]
Message-ID: <49063F75.7000604@sgi.com> (raw)
In-Reply-To: <ge38k5$qf$1@ger.gmane.org>

Michael Lueck wrote:
> No suggestions / possible answers anyone for my question...
> 
> Michael Lueck wrote:
>> Greetings-
>>
>> I hope this is the NNTP equiv of the email list found on this web page:
>> http://oss.sgi.com/projects/xfs/
>>
>> I have been using XFS with Debian for a number of years with great 
>> success. Today, xfsrestore really threw me a curve ball. I am 
>> wondering what went wrong.
>>
>> I had wanted to restore from an old backup some directories that I 
>> discovered I had need of. I used the following syntax to get the 
>> restore started:
>>
>> xfsrestore -J -E -f /mnt/ext_backup/ldslnx01/20061220/data -s 
>> shares/data -i -v verbose /srv
>>
>> I selected some directories to restore through the interactive 
>> interface, then allowed it to restore the specified files.
>>
>> What it ended up doing, HOWEVER, was to restore every file present in 
>> that old backup that was no longer on disk!
>>
>> Thus, what went wrong?
>>
>> Thanks!
> 

Hi Michael,

I tried to reproduce this using the command line you supplied, but
everything worked as expected for me. 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.

Bill

  reply	other threads:[~2008-10-27 22:22 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 [this message]
2008-10-27 23:59     ` Michael Lueck
2008-10-28  2:10       ` Timothy Shimmin
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=49063F75.7000604@sgi.com \
    --to=wkendall@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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox