Bug#421659: cpio: mt does not report tape status and hangs if, the drive is empty

2012-02-03 Thread Peter Maloney
Bug still exists in Ubuntu 10.04.2 with cpio 2.10

$ mt --version
mt (GNU cpio 2.10)

$ cat /etc/lsb-release 
DISTRIB_ID=Ubuntu
DISTRIB_RELEASE=10.04
DISTRIB_CODENAME=lucid
DISTRIB_DESCRIPTION=Ubuntu 10.04.2 LTS

$ cat /etc/debian_version 
squeeze/sid






-- 
To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org
with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org



Bug#421659: cpio: mt does not report tape status and hangs if the drive is empty

2008-08-27 Thread Chris Davies
Just discovered this report. I've also had terrible problems with a more 
recent version of mt. Your suggestion of using mt-st instead works for me. 
Fantastic, thank you.


kernel: 2.6.18-4-xen-686
cpio: cpio/testing uptodate 2.9-13
mt-st: mt-st/testing uptodate 1.1-2

Cheers,
Chris



--
To UNSUBSCRIBE, email to [EMAIL PROTECTED]
with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]



Bug#421659: cpio: mt does not report tape status and hangs if the drive is empty

2007-04-30 Thread Steve Lane
Package: cpio
Version: 2.7-1
Severity: grave
Justification: renders package unusable


Using the cpio 2.6-17 stable version of mt, I can do the following:

  With a tape in the drive:

root /bin/mt -f /dev/nst0 status
drive type = Generic SCSI-2 tape
drive status = 1241513984
sense key error = 0
residue count = 0
file number = 0
block number = 0
Tape block size 0 bytes. Density code 0x4a (unknown).
Soft error count since last status=0
General status bits on (4101):
 BOT ONLINE IM_REP_EN
root

  With no tape in the drive:

root /bin/mt -f /dev/nst0 status
/bin/mt: /dev/nst0: No medium found
root


Using the cpio 2.7-1 testing version of mt, I get this:

  With a tape in the drive:

root /bin/mt -f /dev/nst0 status
drive type = 114
drive status = 1241513984
sense key error = 0
residue count = 0
file number = 0
block number = 0
root

  (i.e. much of the actually useful information I need isn't there.)

  With no tape in the drive:

root /bin/mt -f /dev/nst0 status

  the command just hangs - I have to give it an interrupt (^C) to get
  the prompt back.


In addition, using the 2.7-1 mt has resulted in the drive requesting
the cleaning tape after most uses (60+%).  This behavior did not occur
prior to upgrading to 2.7-1, and has gone away now that I've downgraded
to 2.6-17.

I don't want to upgrade to 2.7-2 because (a) I have no reason to assume
this will solve these problems, and (b) 2.7-2 wants me to upgrade libc6,
which I'm not willing to do for this one package.

Please advise.

Thanks,

--
Steve Lane
System, Network and Security Administrator
Doudna Lab
Biomolecular Structure and Mechanism Group
UC Berkeley

-- System Information:
Debian Release: lenny/sid
  APT prefers testing
  APT policy: (990, 'testing'), (900, 'stable'), (800, 'unstable')
Architecture: i386 (i686)

Kernel: Linux 2.6.15-phabrix060 (SMP w/4 CPU cores)
Locale: LANG=C, LC_CTYPE=C (charmap=ANSI_X3.4-1968)
Shell: /bin/sh linked to /bin/bash

Versions of packages cpio depends on:
ii  libc6   2.3.6.ds1-13 GNU C Library: Shared libraries

cpio recommends no packages.

-- no debconf information


-- 
To UNSUBSCRIBE, email to [EMAIL PROTECTED]
with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]



Bug#421659: cpio: mt does not report tape status and hangs if the drive is empty

2007-04-30 Thread Clint Adams
 Using the cpio 2.6-17 stable version of mt, I can do the following:
[...]
 Using the cpio 2.7-1 testing version of mt, I get this:
[...]
 
 In addition, using the 2.7-1 mt has resulted in the drive requesting
 the cleaning tape after most uses (60+%).  This behavior did not occur
 prior to upgrading to 2.7-1, and has gone away now that I've downgraded
 to 2.6-17.
 
 I don't want to upgrade to 2.7-2 because (a) I have no reason to assume
 this will solve these problems, and (b) 2.7-2 wants me to upgrade libc6,
 which I'm not willing to do for this one package.
 
 Please advise.

Does the mt-st package do what you want?


-- 
To UNSUBSCRIBE, email to [EMAIL PROTECTED]
with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]