public inbox for linux-xfs@vger.kernel.org
 help / color / mirror / Atom feed
From: Donald Douwsma <donaldd@sgi.com>
To: Leon Kolchinsky <leonk@construct.haifa.ac.il>
Cc: 'Olaf Fr?czyk' <olaf@cbk.poznan.pl>,
	'Timothy Shimmin' <tes@sgi.com>,
	xfs@oss.sgi.com
Subject: Re: xfsdump/xfsrestore question
Date: Mon, 26 Feb 2007 16:29:52 +1100	[thread overview]
Message-ID: <45E27050.6080609@sgi.com> (raw)
In-Reply-To: <20070224150933.BFE26200D8@mail.edu.haifa.ac.il>

Leon Kolchinsky wrote:
> 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" /
> #
> 
> So, I've got to Ctrl+C the process.
> 
> Questions:
> 1) What could be the syntax problem in the above command?

The above command seems to have a typo wrt unbalanced quotes.

I'd say the " at the end of line is making the shell hang around
waiting for you to match the quotes (' and ").

So xfsdump is not actually running.

Try

xfsdump -f /data/backup2.file -L 'session1' -M 'media1' /


> 2) Any examples for incremental xfsdump (non-interactive, i.e. run from
> cronjob) would be very welcome (and also comments about xfsrestore from
> these backups).
> 
> On the other hand, interactive xfsdump went fine:

  parent reply	other threads:[~2007-02-26  5:30 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 [this message]
2007-02-26  5:52       ` Timothy Shimmin
2007-02-26 13:16         ` Leon Kolchinsky

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=45E27050.6080609@sgi.com \
    --to=donaldd@sgi.com \
    --cc=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