From: "Leon Kolchinsky" <leonk@construct.haifa.ac.il>
To: 'Timothy Shimmin' <tes@sgi.com>, 'Olaf Fr?czyk' <olaf@cbk.poznan.pl>
Cc: xfs@oss.sgi.com
Subject: RE: xfsdump/xfsrestore question
Date: Mon, 26 Feb 2007 15:16:49 +0200 [thread overview]
Message-ID: <20070226132145.12C281FF44@mail.edu.haifa.ac.il> (raw)
In-Reply-To: <3D67095B5C9E951BA3DB9BD5@timothy-shimmins-power-mac-g5.local>
> > Yep, consistent FS is what I care about in the case of disaster.
> >
> I'm not sure I know exactly what you are getting at.
> After the restore you should have a consistent FS because it is _not_
> a low level filesystem dumper. It is mostly a high lever dump/restore
> program and to the extent that it can generally restore to a foreign
> filesystem e.g. ext2.
> (For example, it does know about file extents but it only uses this info
> on restore to
> preserve holes by seeking and writing.)
> So as it is just doing standard system calls on restore, it can't really
> violate filesystem consistency.
>
>
> > Now, when I've tried to make non-interactive xfsdump I'vo got > prompt
> with
> > no action, like this
> ># xfsdump -f /data/backup2.file -L 'session1' -M 'media1" /
> >>
> Presumably quoting problem as Donald pointed out - it definitely works
> otherwise
> without extra input.
>
Thanks Donald, Timothy
It was indeed quotes problem :)
It's running OK now.
Best Regards,
Leon Kolchinsky
prev parent reply other threads:[~2007-02-26 13:16 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-02-20 14:16 xfsdump/xfsrestore question Leon Kolchinsky
2007-02-20 14:19 ` Justin Piszcz
2007-02-21 0:07 ` Timothy Shimmin
2007-02-21 21:02 ` Leon Kolchinsky
2007-02-22 12:48 ` Olaf Frączyk
2007-02-24 15:04 ` Leon Kolchinsky
2007-02-24 15:10 ` Iustin Pop
2007-02-26 13:14 ` Leon Kolchinsky
2007-02-26 5:29 ` Donald Douwsma
2007-02-26 5:52 ` Timothy Shimmin
2007-02-26 13:16 ` Leon Kolchinsky [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=20070226132145.12C281FF44@mail.edu.haifa.ac.il \
--to=leonk@construct.haifa.ac.il \
--cc=olaf@cbk.poznan.pl \
--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