2.0.33: scsi tape strangeness

eyal (eyal@eyal.emu.id.au)
Mon, 29 Dec 1997 01:09:10 +1100

I have a DDS-I DAT tape, which I used for over three years. My standard
initialization
before a backup involves removing all partitions. No problems there. A
few months
ago I started using a new DDS-II unit, and my DDS-I tape became st1.
Since then the
system thinks that the old unit does not support partitioning. It says:

st1: Mode 0 options: buffer writes: 1, async writes: 1, read ahead: 1
st1: can bsr: 0, two FMs: 0, fast mteom: 0, auto lock: 0,
st1: defs for wr: 0, no block limits: 0, partitions: 0, s2 log: 1

It used to say:
st0: Mode 0 options: buffer writes: 1, async writes: 1, read ahead: 1
st0: can bsr: 0, two FMs: 0, fast mteom: 0, auto lock: 0,
st0: defs for wr: 0, no block limits: 0, partitions: 1, s2 log: 1

The new st0 can partition just fine.

I do not know if this is new to 2.0.33, I just noticed this now.

--
Eyal Lebedinsky		(eyal@eyal.emu.id.au)