From: Gene Heskett <gene.heskett@gmail.com>
To: linux-kernel@vger.kernel.org
Cc: Ray Lee <ray@madrabbit.org>
Subject: Re: New thread RDSL, post-2.6.20 kernels and amanda (tar) miss-fires
Date: Thu, 15 Mar 2007 02:30:33 -0400 [thread overview]
Message-ID: <200703150230.33141.gene.heskett@gmail.com> (raw)
In-Reply-To: <45F8CF68.8060400@madrabbit.org>
On Thursday 15 March 2007, Ray Lee wrote:
>Gene Heskett wrote:
>> Here is an example
>> [root@coyote data]# dd if=00010.coyote._lib.1 bs=32k count=1
>> AMANDA: FILE 20070314104344 coyote /lib lev 1 comp .gz program
>> /bin/tar To restore, position tape at start of file and run:
>> dd if=<tape> bs=32k skip=1 | /bin/gzip -dc | /bin/tar -f - ...
>>
>> And the elipsis is an error if not removed. Then one is supposed to
>> be able to redirect tars output with the usual >/tmp/test/ syntax
>>
>> So:
>> [root@coyote data]# dd if=00010.coyote._lib.1 bs=32k
>> skip=1 | /bin/gzip -dc | /bin/tar -f - >/tmp/test/
>> -bash: /tmp/test/: Is a directory
>>
>> which is the return from any variation in how the redirect is done.
>>
>> So what is it that am I doing wrong in the above command line?, so I
>> can add it to my helper scripts to be published eventually on
>> zmanda.org.
>
>One of us is confused, and it may very well be me, but...
>
>the /bin/tar -f - >/tmp/test/ looks to me like it should fail exactly as
>bash says it does. the output redirect (>) will only write out to a
>file, not a directory. (So, /tmp/file should work, /tmp/file/ won't.)
>
>Are you trying to redirect where the files get restored? That should be
>done with a cd before doing the uncompress.
>
>Or am I misunderstanding what you're telling me?
>
>Ray
No, apparently its me that's been running with a fubar'd understanding.
I was certain that tar (or bash) should have been able to put the
recovered files IN the directory /tmp/test but that turns out to need
more options after the '-f -' section of that sample line I posted.
Thanks. A bunch..
--
Cheers, Gene
"There are four boxes to be used in defense of liberty:
soap, ballot, jury, and ammo. Please use in that order."
-Ed Howdershelt (Author)
Mal: "You are very much lacking in imagination."
Zoe: "I imagine that's so, sir."
--Episode #8, "Out of Gas"
next prev parent reply other threads:[~2007-03-15 6:30 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-03-13 8:28 Gene Heskett
2007-03-13 18:36 ` Gene Heskett
2007-03-14 3:31 ` Gene Heskett
2007-03-14 5:07 ` William Lee Irwin III
2007-03-14 5:44 ` William Lee Irwin III
2007-03-14 6:09 ` Gene Heskett
2007-03-14 6:19 ` William Lee Irwin III
2007-03-14 14:54 ` Gene Heskett
2007-03-14 21:49 ` Ray Lee
2007-03-15 3:12 ` Gene Heskett
2007-03-15 4:45 ` Ray Lee
2007-03-15 6:30 ` Gene Heskett [this message]
2007-03-15 5:28 ` [OT] " Willy Tarreau
2007-03-15 6:33 ` Gene Heskett
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=200703150230.33141.gene.heskett@gmail.com \
--to=gene.heskett@gmail.com \
--cc=linux-kernel@vger.kernel.org \
--cc=ray@madrabbit.org \
/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
all inboxes | Powered by JetHome®