Re: Unable to read/write to a tape with tar

["cyril bonnard" <cyril_bonnard at hotmail dot com>]

After installing the new dll of cygwin, the behaviour of mt changed to:

Administrateur@t-0e0d94b2a0f54 ~
$ strace -o trace.txt mt -f /dev/st0 status
mt: /dev/st0: Bad address

Administrateur@t-0e0d94b2a0f54 ~
$ mt -f /dev/st0 status
drive type = Unknown type of tape device
drive status = 0
sense key error = 0
residue count = 0
file number = -1
block number = -1
Tape block size 0 bytes. Density code 00 (default).
General status bits on (1010000):
ONLINE IM_REP_EN

So i cannot provide you the trace and the stackdump with the new dll, i send 
the stackdump corresponding to the PREVIOUS run and so to the old dll.

Concerning the SEGV, it occurs only while running strace and not while 
running tar/mt alone.

I've attached the cygcheck.

As u noticed, mt status does produce an output with some more information, 
if it could help you in your anlayse...

Thank you for your follow up!

cyril.



> From: Corinna Vinschen <corinna-cygwin@cygwin.com>
> Reply-To: cygwin@cygwin.com
> To: cygwin@cygwin.com
> Subject: Re: Unable to read/write to a tape with tar
> Date: Mon, 22 Aug 2005 16:07:54 +0200
>
> On Aug 22 12:42, cyril bonnard wrote:
> > So, W2k recognizes the device as a "ARCHIVE VIPER 150 21531" and the 
> file
> > pointed for driving is qic157.sys
>
> Er... well, right, there are at least three different tape drive types
> which have been sold as Sun 411 tape drives.
>
> The Archive Viper is a QIC drive, so the driver should be correct.  The
> Viper is known to be some sort of a beast with changing behaviour depending
> of the firmware revision.  Anyway...
>
> > I 've done the strace, [...]
>
> Not exactly.  You made an strace of tar, but I asked for an strace of
> `mt -f /dev/st0 status'.
>
> There's also a SEGV in your strace which you didn't mention before.  Is
> that reproducible?
>
> What I'd like to see is this.  Please download the latest snapshot DLL
> http://cygwin.com/snapshots/cygwin1-20050819.dll.bz2 and install it
> instead of your current Cygwin DLL.  Rename your current Cygwin DLL before,
> so you can move it back to its orignal name when you're done.
>
> Send the output of cygcheck as described on 
> http://cygwin.com/problems.html,
> send the bzip2'ed strace of `mt -f /dev/st0 status` and send the file
> tar.exe.stackdump after you have reproduced the SEGV with the snapshot DLL.
>
>
> Corinna
>
> --
> Corinna Vinschen                  Please, send mails regarding Cygwin to
> Cygwin Project Co-Leader          mailto:cygwin@cygwin.com
> Red Hat, Inc.
>
> --
> Unsubscribe info:      http://cygwin.com/ml/#unsubscribe-simple
> Problem reports:       http://cygwin.com/problems.html
> Documentation:         http://cygwin.com/docs.html
> FAQ:                   http://cygwin.com/faq/

Attachment: cygcheck.out
Description: Binary data

Attachment: mt.exe.stackdump
Description: Binary data

Attachment: tar.exe.stackdump
Description: Binary data

--
Unsubscribe info:      http://cygwin.com/ml/#unsubscribe-simple
Problem reports:       http://cygwin.com/problems.html
Documentation:         http://cygwin.com/docs.html
FAQ:                   http://cygwin.com/faq/