>What does `mt -f /dev/nst0 datcompression` say?

>mt -f /dev/nst0 datcompression
mt: unknown command "datcompression"
usage: mt [-v] [--version] [-h] [ -f device ] command [ count ]
commands: weof, wset, eof, fsf, fsfm, bsf, bsfm, fsr, bsr, fss, bss, rewind, 
          offline, rewoffl, eject, retension, eod, seod, seek, tell, status, 
          erase, setblk, lock, unlock, load, compression, setdensity, 
          drvbuffer, stwrthreshold, stoptions, stsetoptions, stclearoptions, 
          defblksize, defdensity, defdrvbuffer, defcompression, stsetcln, 
          sttimeout, stlongtimeout, densities, setpartition, mkpartition, 
          partseek, asf, stshowopt.

So I tried:
>mt -f /dev/nst0 compression
/dev/nst0: Input/output error

And tried:
>mt -f /dev/nst0 defcompression

No output there.  Here are the messages after I ran those two commands:
>dmesg | tail
st0: Sense Key : Aborted Command [current] 
st0: Add. Sense: Initiator response timeout
st0: Sense Key : Aborted Command [current] 
st0: Add. Sense: Initiator response timeout

>tail /var/log/syslog
Oct 31 14:10:03 backup kernel: st0: Sense Key : Aborted Command [current] 
Oct 31 14:10:03 backup kernel: st0: Add. Sense: Initiator response timeout
Oct 31 14:10:52 backup kernel: st0: Sense Key : Aborted Command [current] 
Oct 31 14:10:52 backup kernel: st0: Add. Sense: Initiator response timeout


>Have you tried dump? 
Yes.  This was also suggested by another person, see below:

<quote from my bacula-users post>
>>Try

>>
>>dd if=/dev/sda of=/dev/nst0 bs=1M count=1000

Tried it.
>d if=/dev/sda of=/dev/nst0 bs=1M count=1000
dd: writing `/dev/nst0': Invalid argument
1+0 records in
0+0 records out
0 bytes (0 B) copied, 10.048 s, 0.0 kB/s

Not sure why /dev/nst0 was invalid.  After I ran this I checked out dmesg and 
syslog:

>tail /var/log/syslog
Oct 31 13:58:31 backup kernel: st0: Sense Key : Aborted Command [current] 
Oct 31 13:58:31 backup kernel: st0: Add. Sense: Initiator response timeout
Oct 31 13:58:31 backup kernel: st0: Can't set default compression.

>dmesg | tail
st0: Sense Key : Aborted Command [current] 
st0: Add. Sense: Initiator response timeout
st0: Can't set default compression.
</end quote>


>What happens if you use /dev/st0 instead of /dev/nst0?

>tar cvf /dev/st0 .
./
./exclude
./logs
./z_backupall
./backup2tape.sh
./backupNetwork.sh
tar: /dev/st0: Cannot write: Invalid argument
tar: Error is not recoverable: exiting now

Syslog and dmesg after running this:
> tail /var/log/syslog
Oct 31 14:17:44 backup kernel: st0: Sense Key : Aborted Command [current] 
Oct 31 14:17:44 backup kernel: st0: Add. Sense: Initiator response timeout
Oct 31 14:17:44 backup kernel: st0: Can't set default compression.

>dmesg | tail
st0: Add. Sense: Initiator response timeout
st0: Can't set default compression.
^^^^ No dates in dmesg... so not sure if that was from the original "mt -f 
/dev/nst0 defcompression" that I tried.

Thanks for looking!  :)

Michael



      

-------------------------------------------------------------------------
This SF.Net email is sponsored by the Moblin Your Move Developer's challenge
Build the coolest Linux based applications with Moblin SDK & win great prizes
Grand prize is a trip for two to an Open Source event anywhere in the world
http://moblin-contest.org/redirect.php?banner_id=100&url=/
_______________________________________________
Bacula-users mailing list
Bacula-users AT lists.sourceforge DOT net
https://lists.sourceforge.net/lists/listinfo/bacula-users