From: prad <prad@towardsfreedom.com>
To: linux-xfs@oss.sgi.com
Subject: Re: xfsrestore seems to hang
Date: Sat, 25 Jun 2011 15:34:55 -0700 [thread overview]
Message-ID: <87r56hleuo.fsf@psinom.home> (raw)
In-Reply-To: 4E065648.4070904@dermichi.com
Michael Weissenbacher <mw@dermichi.com> writes:
> Hi Prad!
>>
>> so is it possible that the xfsrestore system has to go through the
>> motion of handling the entire file even when it's just extracting a
>> small part of it and things will take their time?
>>
> Yes, that's simply the way it works. It has to go through the whole dump
> to restore one file. Same thing as if you used tar. Both were originally
> designed to be written to tape. So if you want to restore single files
> you should look for another solution. I like to use rsync a lot for that.
>
ok thx michael!
glad that's all cleared up now.
so the most intelligent thing to might be to have the xfsdump
filesystems available for that big crash possibility and just work on a
day-to-day basis with rsync which doesn't duplicate certain things i've
found, but seems to be fantastic for ordinary data items.
i found this document while looking for backup strategies:
http://menehune.opt.wfu.edu/Kokua/SGI/007-2862-005/sgi_html/pt01.html
there is a substantial section on xfsdump and xfsrestore as well as
several other tools (no rsync though), so i'm sure i'll find some good
ideas from there on developing an optimal bkp mechanism for our needs.
--
in friendship,
prad
_______________________________________________
xfs mailing list
xfs@oss.sgi.com
http://oss.sgi.com/mailman/listinfo/xfs
prev parent reply other threads:[~2011-06-25 22:39 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-06-25 16:59 xfsrestore seems to hang prad
2011-06-25 18:29 ` prad
2011-06-25 21:42 ` Michael Weissenbacher
2011-06-25 22:34 ` prad [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=87r56hleuo.fsf@psinom.home \
--to=prad@towardsfreedom.com \
--cc=linux-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