RE: problem with tar

RE: problem with tar

[Sean Mitchell]

I think you're specifying your file with the DOS style drive letter and a
colon sort of like

tar xfz D:\file.tar.gz

instead of the Cygwin/UNIX style of

tar xfz //d/file.tar.gz 

Tar sees the d:\{etc} as specifying a remote machine called d.

Cheers,

Sean


-----Original Message-----
From: Terrell Mitchell [ mailto:terrellm@usit.net ]
Sent: Thursday, August 26, 1999 11:41 AM
To: cygwin@sourceware.cygnus.com
Subject: problem with tar


I have set up cygwin b20 on my windows 98 machine for use with perl and
building cpan modules.
When I try to run tar to extract files from an archive that is not in the
current directory I get an error message

cannot execute remote shell:  no such file
cannot open "file name": I/O error
error is not recoverable: exiting now

I have no idea what is wrong with the configuration.

I have tried with COMMAND.COM, 4DOS , 4NT and BASH as the shells.
Any help or pointers would be appreciated.

Thank You
Terrell


--
Want to unsubscribe from this list?
Send a message to cygwin-unsubscribe@sourceware.cygnus.com

--
Want to unsubscribe from this list?
Send a message to cygwin-unsubscribe@sourceware.cygnus.com

RE: problem with tar

[Sean Mitchell]

I think you're specifying your file with the DOS style drive letter and a
colon sort of like

tar xfz D:\file.tar.gz

instead of the Cygwin/UNIX style of

tar xfz //d/file.tar.gz 

Tar sees the d:\{etc} as specifying a remote machine called d.

Cheers,

Sean


-----Original Message-----
From: Terrell Mitchell [ mailto:terrellm@usit.net ]
Sent: Thursday, August 26, 1999 11:41 AM
To: cygwin@sourceware.cygnus.com
Subject: problem with tar


I have set up cygwin b20 on my windows 98 machine for use with perl and
building cpan modules.
When I try to run tar to extract files from an archive that is not in the
current directory I get an error message

cannot execute remote shell:  no such file
cannot open "file name": I/O error
error is not recoverable: exiting now

I have no idea what is wrong with the configuration.

I have tried with COMMAND.COM, 4DOS , 4NT and BASH as the shells.
Any help or pointers would be appreciated.

Thank You
Terrell


--
Want to unsubscribe from this list?
Send a message to cygwin-unsubscribe@sourceware.cygnus.com

--
Want to unsubscribe from this list?
Send a message to cygwin-unsubscribe@sourceware.cygnus.com

problem with tar

[Stephen Hansen]

I'm having problems writing files to tape with the cygwin tar command on
Windows 2000.  I have the tape device [Exabyte EXB SCSI] mounted on
/dev/rmt/n0.  I can create an archive and write whatever files I want to
tape using -cf.  But when I use "tar -rvf  /dev/rmt/n0  [FILE]..." I get
back

FILE
tar: /dev/rmt/n0: Wrote only 0 of 10240 bytes
tar: Error is not recoverable: exiting now

-A and -u produce the same result, as does mounting the device on
/dev/rmt/0.  I would greatly appreciate anyone's recommending how to
solve this problem.

Stephen Hansen


--
Want to unsubscribe from this list?
Check out: http://cygwin.com/ml/#unsubscribe-simple

Re: problem with tar

[Corinna Vinschen]

On Thu, Jun 14, 2001 at 02:31:55PM -0500, Stephen Hansen wrote:
> I'm having problems writing files to tape with the cygwin tar command on
> Windows 2000.  I have the tape device [Exabyte EXB SCSI] mounted on
> /dev/rmt/n0.  I can create an archive and write whatever files I want to
> tape using -cf.  But when I use "tar -rvf  /dev/rmt/n0  [FILE]..." I get
> back
> 
> FILE
> tar: /dev/rmt/n0: Wrote only 0 of 10240 bytes
> tar: Error is not recoverable: exiting now
> 
> -A and -u produce the same result, as does mounting the device on
> /dev/rmt/0.  I would greatly appreciate anyone's recommending how to
> solve this problem.

It's a problem in the current Cygwin DLL. The reason is a call to a
Win32 tape function which expects a size parameter which contains 32
(Bytes) while the buffer needed is actually only 28 Bytes. Weird.

AFAICS, that problem should only shows up when the current blocksize
is not equal to the default block size and it should only occur on W2K.

You should be able to workaround that problem by setting the
current blocksize to variable blocksize:

    $ mt setblk 0

or by setting the current blocksize to the default blocksize
(for example for a DDS-2):

    $ mt status 2
    tape capacity    :  1953251 KB          remaining        :  1952947 KB
    current block    :        7             write protected  :       no
    datcompression   :       on
    min block size   :        1             max block size   :    65536
    def block size   :    16384             cur block size   :     5120
    report setmarks  :      off
    $ mt setblk 16384

However, I have applied a patch to Cygwin which will show up in the
next developers snapshot and in the next official release.

Hope, that helps,
Corinna

-- 
Corinna Vinschen                  Please, send mails regarding Cygwin to
Cygwin Developer                                mailto:cygwin@cygwin.com
Red Hat, Inc.

--
Want to unsubscribe from this list?
Check out: http://cygwin.com/ml/#unsubscribe-simple

Re: Problem with tar

[Earnie Boyd]

--- Doug Wyatt <dwyatt@sunflower.com> wrote:
> Hi,
> 
> I noticed that your cygcheck indicates that there are 3 copies of
> cygwin1.dll installed (d:\bin,d:\usr\local\bin,c:\winnt) - the one in
> c:\winnt is a different version than the other two.  You might want
> to try reducing those to only one.  And, you might want to try a
> newer version.
> 

Yes, under no circumstance should you have more than one cygwin dll in the
path.  The newer versions are a little more safe in that if more than one
cygwin dll tries to get instantiated then the second occurance will fail to do
so.


=====
Earnie Boyd < mailto:earnie_boyd@yahoo.com >
Cygwin Newbies, please visit
< http://www.freeyellow.com/members5/gw32/index.html >
__________________________________________________
Do You Yahoo!?
Thousands of Stores.  Millions of Products.  All in one place.
Yahoo! Shopping: http://shopping.yahoo.com

--
Want to unsubscribe from this list?
Send a message to cygwin-unsubscribe@sourceware.cygnus.com

Re: Problem with tar

[Earnie Boyd]

--- Doug Wyatt <dwyatt@sunflower.com> wrote:
> Hi,
> 
> I noticed that your cygcheck indicates that there are 3 copies of
> cygwin1.dll installed (d:\bin,d:\usr\local\bin,c:\winnt) - the one in
> c:\winnt is a different version than the other two.  You might want
> to try reducing those to only one.  And, you might want to try a
> newer version.
> 

Yes, under no circumstance should you have more than one cygwin dll in the
path.  The newer versions are a little more safe in that if more than one
cygwin dll tries to get instantiated then the second occurance will fail to do
so.


=====
Earnie Boyd < mailto:earnie_boyd@yahoo.com >
Cygwin Newbies, please visit
< http://www.freeyellow.com/members5/gw32/index.html >
__________________________________________________
Do You Yahoo!?
Thousands of Stores.  Millions of Products.  All in one place.
Yahoo! Shopping: http://shopping.yahoo.com

--
Want to unsubscribe from this list?
Send a message to cygwin-unsubscribe@sourceware.cygnus.com

Re: Problem with tar

[N8TM]

In a message dated 11/26/99 3:53:58 AM Pacific Standard Time, mortene@sim.no 
writes:

> have there been, any know problems with tar or the
>  cygwin.dll in Cygwin
Yes, tar has been one of the first things I tested when installing cygwin 
snapshots, and a number of them have failed.  As for combining cygwin-b19 
with NT4 SP4, I would be surprised if that combination had been tested 
adequately.

Tim
tprince@computer.org

--
Want to unsubscribe from this list?
Send a message to cygwin-unsubscribe@sourceware.cygnus.com

Re: Problem with tar

[N8TM]

In a message dated 11/26/99 3:53:58 AM Pacific Standard Time, mortene@sim.no 
writes:

> have there been, any know problems with tar or the
>  cygwin.dll in Cygwin
Yes, tar has been one of the first things I tested when installing cygwin 
snapshots, and a number of them have failed.  As for combining cygwin-b19 
with NT4 SP4, I would be surprised if that combination had been tested 
adequately.

Tim
tprince@computer.org

--
Want to unsubscribe from this list?
Send a message to cygwin-unsubscribe@sourceware.cygnus.com

Problem with tar

[Morten Eriksen]

Hi,

I have a problem with Cygwin tar which I have a hard time figuring out how
to solve, and I'm hoping someone here can give me a few hints.

Background: I'm partly responsible for administrating 30 remote WinNT
servers (don't ask..), and to fetch data from these servers to include in
a local site backup I use a combination of ssh, tar and scp (sshd has been
installed on the WinNT servers.) 

Every night, for each of the servers, I run approximately this sequence of
commands:

ssh -x -l administrator $ntserver "/bin/tar cvzf /tmp/data.tgz /data"
scp administrator@$ntserver:/tmp/data.tgz data-$ntserver.tgz

Works like a charm, except that tar hangs at what seems like random places
at what seems like random times at what seems like random sites. :^(
Out of the 30 servers, 2-3 on average have this problem every night, and I
have to manually kill the ssh process when I come to work in the morning.
I can't see no patterns on with which sites gets the problem or the data
which tar was trying to read when the hang occurred. Manually running tar
again on the same data doesn't hang again in a reproducible way.

Are there, or have there been, any know problems with tar or the
cygwin.dll in Cygwin which could cause this? If not, does anyone have any
ideas on how I could debug this problem? Any help would be greatly
appreciated.

I have attached the output from "cygcheck.exe -s -r -v" in case that is of
any help. "/bin/tar --version" says "tar (GNU tar) 1.12". 


Regards,
Morten Eriksen

Re: Problem with tar

[Donald E. Hammond]

Morten -

I've had problems in the past using compression on the fly with tar.  It
was different than you describe, and it was with b18 so may not be
relevant, but it does seem to be fixed with v 1.0 from cd.  Sometimes a
tar file that had been compressed with -z was corrupt.  I am *pretty*
sure that it could always be decompressed with gzip -d then untarred,
but testing (-t or -d) and extraction of the compressed tar file all
failed.  Like I say, this seems to be fixed with the latest version but
I haven't done much testing.  I don't know how much data you're putting
in the tar files, but if it wouldn't be too unwieldy I might try doing
it without compression. Or even by compressing each file before putting
it in the tar file.  Even if that's not an acceptable final solution, it
might help isolate the problem.

This is probably completely unrelated to your problem.  For me, tar
never bombed while creating the tar file.  I only knew there was a
problem when trying to read it while decompressing it on the fly.  But
I  thought I'd mention it just in case.

 - Don


Morten Eriksen wrote:
> 
> [...]
> 
> Every night, for each of the servers, I run approximately this sequence of
> commands:
> 
> ssh -x -l administrator $ntserver "/bin/tar cvzf /tmp/data.tgz /data"
> scp administrator@$ntserver:/tmp/data.tgz data-$ntserver.tgz
> 
> Works like a charm, except that tar hangs at what seems like random places
> at what seems like random times at what seems like random sites. :^(
>
> [...]

--
Want to unsubscribe from this list?
Send a message to cygwin-unsubscribe@sourceware.cygnus.com

Re: Problem with tar

[Donald E. Hammond]

Morten -

I've had problems in the past using compression on the fly with tar.  It
was different than you describe, and it was with b18 so may not be
relevant, but it does seem to be fixed with v 1.0 from cd.  Sometimes a
tar file that had been compressed with -z was corrupt.  I am *pretty*
sure that it could always be decompressed with gzip -d then untarred,
but testing (-t or -d) and extraction of the compressed tar file all
failed.  Like I say, this seems to be fixed with the latest version but
I haven't done much testing.  I don't know how much data you're putting
in the tar files, but if it wouldn't be too unwieldy I might try doing
it without compression. Or even by compressing each file before putting
it in the tar file.  Even if that's not an acceptable final solution, it
might help isolate the problem.

This is probably completely unrelated to your problem.  For me, tar
never bombed while creating the tar file.  I only knew there was a
problem when trying to read it while decompressing it on the fly.  But
I  thought I'd mention it just in case.

 - Don


Morten Eriksen wrote:
> 
> [...]
> 
> Every night, for each of the servers, I run approximately this sequence of
> commands:
> 
> ssh -x -l administrator $ntserver "/bin/tar cvzf /tmp/data.tgz /data"
> scp administrator@$ntserver:/tmp/data.tgz data-$ntserver.tgz
> 
> Works like a charm, except that tar hangs at what seems like random places
> at what seems like random times at what seems like random sites. :^(
>
> [...]

--
Want to unsubscribe from this list?
Send a message to cygwin-unsubscribe@sourceware.cygnus.com

Re: Problem with tar

[Doug Wyatt]

Hi,

I noticed that your cygcheck indicates that there are 3 copies of
cygwin1.dll installed (d:\bin,d:\usr\local\bin,c:\winnt) - the one in
c:\winnt is a different version than the other two.  You might want
to try reducing those to only one.  And, you might want to try a
newer version.

If you've got the disk space, you might try  uncompressed tar and
then gzip'ing the resulting archive.  Also, you might try redirecting
stdout and stderr to a file on the remote system to reduce the
possibility that a bad connection over ssh might be hanging the
process.

Is it possible that a remote batch job is working in the /data area
at the same time you're trying to do the backup?

Don't know if any of this will help.

Regards,
Doug Wyatt


> Hi,
> 
> I have a problem with Cygwin tar which I have a hard time figuring out how
> to solve, and I'm hoping someone here can give me a few hints.
> 
> Background: I'm partly responsible for administrating 30 remote WinNT
> servers (don't ask..), and to fetch data from these servers to include in
> a local site backup I use a combination of ssh, tar and scp (sshd has been
> installed on the WinNT servers.) 
> 
> Every night, for each of the servers, I run approximately this sequence of
> commands:
> 
> ssh -x -l administrator $ntserver "/bin/tar cvzf /tmp/data.tgz /data"
> scp administrator@$ntserver:/tmp/data.tgz data-$ntserver.tgz
> 
> Works like a charm, except that tar hangs at what seems like random places
> at what seems like random times at what seems like random sites. :^(
> Out of the 30 servers, 2-3 on average have this problem every night, and I
> have to manually kill the ssh process when I come to work in the morning.
> I can't see no patterns on with which sites gets the problem or the data
> which tar was trying to read when the hang occurred. Manually running tar
> again on the same data doesn't hang again in a reproducible way.
> 
> Are there, or have there been, any know problems with tar or the
> cygwin.dll in Cygwin which could cause this? If not, does anyone have any
> ideas on how I could debug this problem? Any help would be greatly
> appreciated.
> 
> I have attached the output from "cygcheck.exe -s -r -v" in case that is of
> any help. "/bin/tar --version" says "tar (GNU tar) 1.12". 
> 
> 
> Regards,
> Morten Eriksen
> 



--
Want to unsubscribe from this list?
Send a message to cygwin-unsubscribe@sourceware.cygnus.com

Re: Problem with tar

[Doug Wyatt]

Hi,

I noticed that your cygcheck indicates that there are 3 copies of
cygwin1.dll installed (d:\bin,d:\usr\local\bin,c:\winnt) - the one in
c:\winnt is a different version than the other two.  You might want
to try reducing those to only one.  And, you might want to try a
newer version.

If you've got the disk space, you might try  uncompressed tar and
then gzip'ing the resulting archive.  Also, you might try redirecting
stdout and stderr to a file on the remote system to reduce the
possibility that a bad connection over ssh might be hanging the
process.

Is it possible that a remote batch job is working in the /data area
at the same time you're trying to do the backup?

Don't know if any of this will help.

Regards,
Doug Wyatt


> Hi,
> 
> I have a problem with Cygwin tar which I have a hard time figuring out how
> to solve, and I'm hoping someone here can give me a few hints.
> 
> Background: I'm partly responsible for administrating 30 remote WinNT
> servers (don't ask..), and to fetch data from these servers to include in
> a local site backup I use a combination of ssh, tar and scp (sshd has been
> installed on the WinNT servers.) 
> 
> Every night, for each of the servers, I run approximately this sequence of
> commands:
> 
> ssh -x -l administrator $ntserver "/bin/tar cvzf /tmp/data.tgz /data"
> scp administrator@$ntserver:/tmp/data.tgz data-$ntserver.tgz
> 
> Works like a charm, except that tar hangs at what seems like random places
> at what seems like random times at what seems like random sites. :^(
> Out of the 30 servers, 2-3 on average have this problem every night, and I
> have to manually kill the ssh process when I come to work in the morning.
> I can't see no patterns on with which sites gets the problem or the data
> which tar was trying to read when the hang occurred. Manually running tar
> again on the same data doesn't hang again in a reproducible way.
> 
> Are there, or have there been, any know problems with tar or the
> cygwin.dll in Cygwin which could cause this? If not, does anyone have any
> ideas on how I could debug this problem? Any help would be greatly
> appreciated.
> 
> I have attached the output from "cygcheck.exe -s -r -v" in case that is of
> any help. "/bin/tar --version" says "tar (GNU tar) 1.12". 
> 
> 
> Regards,
> Morten Eriksen
> 



--
Want to unsubscribe from this list?
Send a message to cygwin-unsubscribe@sourceware.cygnus.com

Re: Problem with tar

[Morten Eriksen]

[I had a problem with random hangs when ssh'ing into a WinNT server
and running Cygwin tar remotely.]

Just in case anyone is interested; it seems that the problem goes away
when I run tar without the verbose option. So this hangs in random
places at random times (with GNU tar 1.12, NT sshd v1.2.26, HP-UX ssh
v1.2.27):

$ ssh -x -n -l administrator <ntserver> "/bin/tar cvzf <arch> <dir>"

..while this works with no problems:

$ ssh -x -n -l administrator <ntserver> "/bin/tar czf <arch> <dir>"

I'll leave it at that, since it now Works For Me.

Regards,
Morten Eriksen

--
Want to unsubscribe from this list?
Send a message to cygwin-unsubscribe@sourceware.cygnus.com

Re: Problem with tar

[Morten Eriksen]

[I had a problem with random hangs when ssh'ing into a WinNT server
and running Cygwin tar remotely.]

Just in case anyone is interested; it seems that the problem goes away
when I run tar without the verbose option. So this hangs in random
places at random times (with GNU tar 1.12, NT sshd v1.2.26, HP-UX ssh
v1.2.27):

$ ssh -x -n -l administrator <ntserver> "/bin/tar cvzf <arch> <dir>"

..while this works with no problems:

$ ssh -x -n -l administrator <ntserver> "/bin/tar czf <arch> <dir>"

I'll leave it at that, since it now Works For Me.

Regards,
Morten Eriksen

--
Want to unsubscribe from this list?
Send a message to cygwin-unsubscribe@sourceware.cygnus.com

Problem with tar

[Morten Eriksen]

Hi,

I have a problem with Cygwin tar which I have a hard time figuring out how
to solve, and I'm hoping someone here can give me a few hints.

Background: I'm partly responsible for administrating 30 remote WinNT
servers (don't ask..), and to fetch data from these servers to include in
a local site backup I use a combination of ssh, tar and scp (sshd has been
installed on the WinNT servers.) 

Every night, for each of the servers, I run approximately this sequence of
commands:

ssh -x -l administrator $ntserver "/bin/tar cvzf /tmp/data.tgz /data"
scp administrator@$ntserver:/tmp/data.tgz data-$ntserver.tgz

Works like a charm, except that tar hangs at what seems like random places
at what seems like random times at what seems like random sites. :^(
Out of the 30 servers, 2-3 on average have this problem every night, and I
have to manually kill the ssh process when I come to work in the morning.
I can't see no patterns on with which sites gets the problem or the data
which tar was trying to read when the hang occurred. Manually running tar
again on the same data doesn't hang again in a reproducible way.

Are there, or have there been, any know problems with tar or the
cygwin.dll in Cygwin which could cause this? If not, does anyone have any
ideas on how I could debug this problem? Any help would be greatly
appreciated.

I have attached the output from "cygcheck.exe -s -r -v" in case that is of
any help. "/bin/tar --version" says "tar (GNU tar) 1.12". 


Regards,
Morten Eriksen

Re: problem with tar

[Earnie Boyd]

--- Terrell Mitchell <terrellm@usit.net> wrote:
> I have set up cygwin b20 on my windows 98 machine for use with perl and
> building cpan modules.
> When I try to run tar to extract files from an archive that is not in the
> current directory I get an error message
> 
> cannot execute remote shell:  no such file
> cannot open "file name": I/O error
> error is not recoverable: exiting now
> 
> I have no idea what is wrong with the configuration.
> 
> I have tried with COMMAND.COM, 4DOS , 4NT and BASH as the shells.
> Any help or pointers would be appreciated.

It is most likely that you've environment problems.  Please, read my webpage
and then if you still have problems send a plain text output of `cygcheck -s -v -r'.
===
Earnie Boyd < mailto:earnie_boyd@yahoo.com >

Newbies, please visit
< http://www.freeyellow.com/members5/gw32/index.html >

(If you respond to the list, then please don't cc me)
__________________________________________________
Do You Yahoo!?
Bid and sell for free at http://auctions.yahoo.com


--
Want to unsubscribe from this list?
Send a message to cygwin-unsubscribe@sourceware.cygnus.com

Re: problem with tar

[Earnie Boyd]

--- Terrell Mitchell <terrellm@usit.net> wrote:
> I have set up cygwin b20 on my windows 98 machine for use with perl and
> building cpan modules.
> When I try to run tar to extract files from an archive that is not in the
> current directory I get an error message
> 
> cannot execute remote shell:  no such file
> cannot open "file name": I/O error
> error is not recoverable: exiting now
> 
> I have no idea what is wrong with the configuration.
> 
> I have tried with COMMAND.COM, 4DOS , 4NT and BASH as the shells.
> Any help or pointers would be appreciated.

It is most likely that you've environment problems.  Please, read my webpage
and then if you still have problems send a plain text output of `cygcheck -s -v -r'.
===
Earnie Boyd < mailto:earnie_boyd@yahoo.com >

Newbies, please visit
< http://www.freeyellow.com/members5/gw32/index.html >

(If you respond to the list, then please don't cc me)
__________________________________________________
Do You Yahoo!?
Bid and sell for free at http://auctions.yahoo.com


--
Want to unsubscribe from this list?
Send a message to cygwin-unsubscribe@sourceware.cygnus.com

problem with tar

[Terrell Mitchell]

I have set up cygwin b20 on my windows 98 machine for use with perl and
building cpan modules.
When I try to run tar to extract files from an archive that is not in the
current directory I get an error message

cannot execute remote shell:  no such file
cannot open "file name": I/O error
error is not recoverable: exiting now

I have no idea what is wrong with the configuration.

I have tried with COMMAND.COM, 4DOS , 4NT and BASH as the shells.
Any help or pointers would be appreciated.

Thank You
Terrell


--
Want to unsubscribe from this list?
Send a message to cygwin-unsubscribe@sourceware.cygnus.com

problem with tar

[Terrell Mitchell]

I have set up cygwin b20 on my windows 98 machine for use with perl and
building cpan modules.
When I try to run tar to extract files from an archive that is not in the
current directory I get an error message

cannot execute remote shell:  no such file
cannot open "file name": I/O error
error is not recoverable: exiting now

I have no idea what is wrong with the configuration.

I have tried with COMMAND.COM, 4DOS , 4NT and BASH as the shells.
Any help or pointers would be appreciated.

Thank You
Terrell


--
Want to unsubscribe from this list?
Send a message to cygwin-unsubscribe@sourceware.cygnus.com