[ I'm not on this mailing-list, please c the answer, thank you ]
I just tried out 2.1.130 (first contact with 2.1.x) and just noticed a slight
change in behavior of st.o:
~-0# mt -f /dev/nst0 eod
~-0# mt -f /dev/nst0 status
SCSI 2 tape drive:
File number=110, block number=0, partition=0.
Tape block size 1024 bytes. Density code 0x15 (EXB-8500 (RLL 45434 bpi)).
Soft error count since last status=0
General status bits on (89010000):
EOF EOD ONLINE IM_REP_EN
~-1# dd bs=128b if=/home/ftp/softs/linux/kernel/linux-2.1.130.tar.bz2
of=/dev/nst0
dd: /dev/nst0: Input/output error
154+1 records in
154+0 records out
~-1# mt -f /dev/nst0 status
SCSI 2 tape drive:
File number=111, block number=0, partition=0.
Tape block size 1024 bytes. Density code 0x15 (EXB-8500 (RLL 45434 bpi)).
Soft error count since last status=0
General status bits on (81010000):
EOF ONLINE IM_REP_EN
Here we notice that the `mt status' after an append only has `EOF' while
on 2.0.36 (and previous 2.0.x as well AFAIK) there would be `EOF' *and* `EOD'.
Has it been changed purposefully or accidentally ?
Another thing:
Right after doing the above, I did (I use kmod):
~-0# rmmod st
~-0# mt -f /dev/nst0 status
SCSI 2 tape drive:
File number=0, block number=0, partition=0.
Tape block size 1024 bytes. Density code 0x15 (EXB-8500 (RLL 45434 bpi)).
Soft error count since last status=0
General status bits on (41010000):
BOT ONLINE IM_REP_EN
This `BOT' is clearly wrong since the tape is still positioned at
filenumber=111.
Stefan "quite happy with its new 2.1 kernel"
-
To unsubscribe from this list: send the line "unsubscribe linux-scsi" in
the body of a message to [EMAIL PROTECTED]
