Problem mounting HP LTO5 with HP LTFS 2.1.0

1,121 views
Skip to first unread message

Patrick Dung

unread,
Jul 26, 2013, 12:17:48 PM7/26/13
to quadst...@googlegroups.com
Hi quadstor,

I am emulating HP LTO5 drive using quadstor 2.2.8.
I can format the tape as ltfs but I am unable to mount it.

I have no problem using:
IBM LTO5 emulation with IBM lin_tape, IBM ltfs 1.3.
Quadstor 2.2.7.


I get the HP 2.1.0 LTFS from here:
http://h20000.www2.hp.com/bizsupport/TechSupport/SoftwareDescription.jsp?lang=en&cc=us&prodTypeId=12169&prodSeriesId=4249221&prodNameId=4249245&swEnvOID=4006&swLang=13&mode=2&taskId=135&swItem=co-119743-1

# /usr/local/bin/ltfs -V
HP LTFS standalone version 2.1.0
LTFS Format Specification version 2.1.0

# mkltfs -d /dev/st4
LTFS15000I Starting mkltfs, LTFS version 2.1.0, log level 2
LTFS15041I Launched by "mkltfs -d /dev/st4"
LTFS15042I This binary is built for Linux (x86_64)
LTFS15043I GCC version is 4.1.2 20080704 (Red Hat 4.1.2-48)
LTFS17087I Kernel version: Linux version 2.6.32-358.el6.x86_64 (mock...@x86-022.build.eng.bos.redhat.com) (gcc version 4.4.7 20120313 (Red Hat 4.4.7-3) (GCC) ) #1 SMP Tue Jan 29 11:47:41 EST 2013 x86_64
LTFS17089I Distribution: LSB_VERSION=base-4.0-amd64:base-4.0-noarch:core-4.0-amd64:core-4.0-noarch:graphics-4.0-amd64:graphics-4.0-noarch:printing-4.0-amd64:printing-4.0-noarch
LTFS17089I Distribution: Red Hat Enterprise Linux Server release 6.4 (Santiago)
LTFS17089I Distribution: Red Hat Enterprise Linux Server release 6.4 (Santiago)
LTFS15003I Formatting device '/dev/st4'
LTFS15004I LTFS volume blocksize: 524288
LTFS15005I Index partition placement policy: None

LTFS17085I Plugin: Loading "ltotape" driver
LTFS20013I Drive type is HP LTO5, serial number is QDRS000000
LTFS17160I Maximum device block size is 524288
LTFS15049I Checking the medium
LTFS11175E Cannot read ANSI label: expected 80 bytes, but received 4096
LTFS11009E Cannot read volume: failed to read partition labels.
LTFS15010I Creating data partition b on SCSI partition 1
LTFS15011I Creating index partition a on SCSI partition 0
LTFS17165I Resetting the medium's capacity proportion
LTFS11097I Partitioning the medium
LTFS11100I Writing label to partition b
LTFS11278I Writing index to partition b
LTFS11100I Writing label to partition a
LTFS11278I Writing index to partition a
LTFS15013I Volume UUID is: ce83e9fb-1ec7-431f-87f0-219fb17a7218

LTFS15019I Volume capacity is 1473 GB
LTFS20076I Triggering drive diagnostic dump
LTFS20077W Unable to generate drive dump
LTFS20096I Diagnostic dump complete
LTFS15024I Medium formatted successfully

# ltfs /mnt-ltfs -o devname=/dev/st4
LTFS14000I LTFS starting, LTFS version 2.1.0, log level 2
LTFS14058I LTFS Format Specification version 2.1.0
LTFS14104I Launched by "ltfs /mnt-ltfs -o devname=/dev/st4"
LTFS14105I This binary is built for Linux (x86_64)
LTFS14106I GCC version is 4.1.2 20080704 (Red Hat 4.1.2-48)
LTFS17087I Kernel version: Linux version 2.6.32-358.el6.x86_64 (mock...@x86-022.build.eng.bos.redhat.com) (gcc version 4.4.7 20120313 (Red Hat 4.4.7-3) (GCC) ) #1 SMP Tue Jan 29 11:47:41 EST 2013 x86_64
LTFS17089I Distribution: LSB_VERSION=base-4.0-amd64:base-4.0-noarch:core-4.0-amd64:core-4.0-noarch:graphics-4.0-amd64:graphics-4.0-noarch:printing-4.0-amd64:printing-4.0-noarch
LTFS17089I Distribution: Red Hat Enterprise Linux Server release 6.4 (Santiago)
LTFS17089I Distribution: Red Hat Enterprise Linux Server release 6.4 (Santiago)
LTFS14063I Sync type is "time", Sync time is 300 sec
LTFS17085I Plugin: Loading "ltotape" driver
LTFS17085I Plugin: Loading "unified" iosched
LTFS20013I Drive type is HP LTO5, serial number is QDRS000000
LTFS17160I Maximum device block size is 524288
LTFS11005I Mounting the volume
LTFS11197E Cannot read index: back pointer is corrupt
LTFS11024E Cannot mount volume: read index failed on the index partition
LTFS14013E Cannot mount the volume
LTFS20076I Triggering drive diagnostic dump
LTFS20077W Unable to generate drive dump
LTFS20096I Diagnostic dump complete

# ltfs /mnt-ltfs -o devname=/dev/st4 -o trace
LTFS14000I LTFS starting, LTFS version 2.1.0, log level 3
LTFS14058I LTFS Format Specification version 2.1.0
LTFS14104I Launched by "ltfs /mnt-ltfs -o devname=/dev/st4 -o trace"
LTFS14105I This binary is built for Linux (x86_64)
LTFS14106I GCC version is 4.1.2 20080704 (Red Hat 4.1.2-48)
LTFS17087I Kernel version: Linux version 2.6.32-358.el6.x86_64 (mock...@x86-022.build.eng.bos.redhat.com) (gcc version 4.4.7 20120313 (Red Hat 4.4.7-3) (GCC) ) #1 SMP Tue Jan 29 11:47:41 EST 2013 x86_64
LTFS17089I Distribution: LSB_VERSION=base-4.0-amd64:base-4.0-noarch:core-4.0-amd64:core-4.0-noarch:graphics-4.0-amd64:graphics-4.0-noarch:printing-4.0-amd64:printing-4.0-noarch
LTFS17089I Distribution: Red Hat Enterprise Linux Server release 6.4 (Santiago)
LTFS17089I Distribution: Red Hat Enterprise Linux Server release 6.4 (Santiago)
LTFS14063I Sync type is "time", Sync time is 300 sec
LTFS17085I Plugin: Loading "ltotape" driver
LTFS17085I Plugin: Loading "unified" iosched
LTFS20031D Looking for sg device corresponding to /dev/st4
LTFS20034D Mapped /dev/st4 to /dev/sg15 (4.0.0.0)
LTFS20020D SG_RESERVED_SIZE (max block size) now set to 524288 bytes
LTFS20010D SCSI request: [ 12 00 00 00 F0 00 ] Requested length=240
LTFS20011D SCSI outcome: Driver status=0x00 SCSI status=0x00 Actual length=96
LTFS20084D Drive identification is 'Ultrium 5-SCSI  '
LTFS20010D SCSI request: [ 12 01 80 00 20 00 ] Requested length=32
LTFS20011D SCSI outcome: Driver status=0x00 SCSI status=0x00 Actual length=14
LTFS20013I Drive type is HP LTO5, serial number is QDRS000000
LTFS20010D SCSI request: [ 00 00 00 00 00 00 ] Requested length=0
LTFS20011D SCSI outcome: Driver status=0x00 SCSI status=0x00 Actual length=0
LTFS20061D Backend modesense: 0x11
LTFS20010D SCSI request: [ 5A 00 51 00 00 00 00 00 20 00 ] Requested length=32
LTFS20011D SCSI outcome: Driver status=0x00 SCSI status=0x00 Actual length=32
LTFS12023D Reserving device
LTFS20010D SCSI request: [ 16 00 00 00 00 00 ] Requested length=0
LTFS20011D SCSI outcome: Driver status=0x00 SCSI status=0x00 Actual length=0
LTFS20061D Backend modesense: 0x00
LTFS20010D SCSI request: [ 5A 00 00 00 00 00 00 00 08 00 ] Requested length=8
LTFS20011D SCSI outcome: Driver status=0x00 SCSI status=0x00 Actual length=8
LTFS20010D SCSI request: [ 05 00 00 00 00 00 ] Requested length=6
LTFS20011D SCSI outcome: Driver status=0x00 SCSI status=0x00 Actual length=6
LTFS17160I Maximum device block size is 524288
LTFS20010D SCSI request: [ 00 00 00 00 00 00 ] Requested length=0
LTFS20011D SCSI outcome: Driver status=0x00 SCSI status=0x00 Actual length=0
LTFS20061D Backend logsense: 0x31
LTFS20010D SCSI request: [ 4D 00 71 00 00 00 00 04 00 00 ] Requested length=1024
LTFS20011D SCSI outcome: Driver status=0x00 SCSI status=0x00 Actual length=36
LTFS20057D Backend capacity part0: (87744, 87744)
LTFS20057D Backend capacity part1: (1448128, 1448256)
LTFS20061D Backend modesense: 0x10
LTFS20010D SCSI request: [ 5A 00 10 01 00 00 00 00 30 00 ] Requested length=48
LTFS20011D SCSI outcome: Driver status=0x00 SCSI status=0x00 Actual length=48
LTFS20010D SCSI request: [ 55 10 00 00 00 00 00 00 30 00 ] Requested length=48
LTFS20011D SCSI outcome: Driver status=0x00 SCSI status=0x00 Actual length=48
LTFS20061D Backend modesense: 0x10
LTFS20010D SCSI request: [ 5A 00 10 01 00 00 00 00 30 00 ] Requested length=48
LTFS20011D SCSI outcome: Driver status=0x00 SCSI status=0x00 Actual length=48
LTFS11005I Mounting the volume
LTFS11012D Loading the tape
LTFS20010D SCSI request: [ 00 00 00 00 00 00 ] Requested length=0
LTFS20011D SCSI outcome: Driver status=0x00 SCSI status=0x00 Actual length=0
LTFS20010D SCSI request: [ 1B 00 00 00 01 00 ] Requested length=0
LTFS20011D SCSI outcome: Driver status=0x00 SCSI status=0x00 Actual length=0
LTFS20010D SCSI request: [ 34 06 00 00 00 00 00 00 00 00 ] Requested length=32
LTFS20011D SCSI outcome: Driver status=0x00 SCSI status=0x00 Actual length=32
LTFS20060D Backend ReadPosition: Partition=0, LogObject=0, FMcount=0
LTFS20061D Backend modesense: 0x1D
LTFS20010D SCSI request: [ 5A 00 1D 00 00 00 00 00 40 00 ] Requested length=64
LTFS20011D SCSI outcome: Driver status=0x00 SCSI status=0x00 Actual length=48
LTFS20010D SCSI request: [ 00 00 00 00 00 00 ] Requested length=0
LTFS20011D SCSI outcome: Driver status=0x00 SCSI status=0x00 Actual length=0
LTFS12026D Locking medium in the drive
LTFS20010D SCSI request: [ 1E 00 00 00 01 00 ] Requested length=0
LTFS20011D SCSI outcome: Driver status=0x00 SCSI status=0x00 Actual length=0
LTFS20010D SCSI request: [ 34 06 00 00 00 00 00 00 00 00 ] Requested length=32
LTFS20011D SCSI outcome: Driver status=0x00 SCSI status=0x00 Actual length=32
LTFS20060D Backend ReadPosition: Partition=0, LogObject=0, FMcount=0
LTFS20061D Backend modesense: 0x00
LTFS20010D SCSI request: [ 5A 00 00 00 00 00 00 00 10 00 ] Requested length=16
LTFS20011D SCSI outcome: Driver status=0x00 SCSI status=0x00 Actual length=16
LTFS20010D SCSI request: [ 55 10 00 00 00 00 00 00 10 00 ] Requested length=16
LTFS20011D SCSI outcome: Driver status=0x00 SCSI status=0x00 Actual length=16
LTFS20061D Backend logsense: 0x31
LTFS20010D SCSI request: [ 4D 00 71 00 00 00 00 04 00 00 ] Requested length=1024
LTFS20011D SCSI outcome: Driver status=0x00 SCSI status=0x00 Actual length=36
LTFS20057D Backend capacity part0: (87744, 87744)
LTFS20057D Backend capacity part1: (1448128, 1448256)
LTFS20061D Backend modesense: 0x00
LTFS20010D SCSI request: [ 5A 00 00 00 00 00 00 00 08 00 ] Requested length=8
LTFS20011D SCSI outcome: Driver status=0x00 SCSI status=0x00 Actual length=8
LTFS20010D SCSI request: [ 05 00 00 00 00 00 ] Requested length=6
LTFS20011D SCSI outcome: Driver status=0x00 SCSI status=0x00 Actual length=6
LTFS20061D Backend modesense: 0x10
LTFS20010D SCSI request: [ 5A 00 10 01 00 00 00 00 30 00 ] Requested length=48
LTFS20011D SCSI outcome: Driver status=0x00 SCSI status=0x00 Actual length=48
LTFS11007D Tape is loaded
LTFS20061D Backend logsense: 0x31
LTFS20010D SCSI request: [ 4D 00 71 00 00 00 00 04 00 00 ] Requested length=1024
LTFS20011D SCSI outcome: Driver status=0x00 SCSI status=0x00 Actual length=36
LTFS20057D Backend capacity part0: (87744, 87744)
LTFS20057D Backend capacity part1: (1448128, 1448256)
LTFS11008D Reading partition labels
LTFS20061D Backend modesense: 0x00
LTFS20010D SCSI request: [ 5A 00 00 00 00 00 00 00 08 00 ] Requested length=8
LTFS20011D SCSI outcome: Driver status=0x00 SCSI status=0x00 Actual length=8
LTFS20010D SCSI request: [ 05 00 00 00 00 00 ] Requested length=6
LTFS20011D SCSI outcome: Driver status=0x00 SCSI status=0x00 Actual length=6
LTFS20039D Backend read: 4096 bytes
LTFS20010D SCSI request: [ 08 02 00 10 00 00 ] Requested length=4096
LTFS20011D SCSI outcome: Driver status=0x00 SCSI status=0x00 Actual length=80
LTFS20039D Backend read: 4096 bytes
LTFS20010D SCSI request: [ 08 02 00 10 00 00 ] Requested length=4096
LTFS20011D SCSI outcome: Driver status=0x00 SCSI status=0x02 Actual length=0
LTFS20012D SCSI sense  : F0 00 80 00 00 10 00 0A 00 00 00 00 00 01 00 00 00 00
LTFS20038D Read block: file mark detected
LTFS20039D Backend read: 4096 bytes
LTFS20010D SCSI request: [ 08 02 00 10 00 00 ] Requested length=4096
LTFS20011D SCSI outcome: Driver status=0x00 SCSI status=0x00 Actual length=477
LTFS20039D Backend read: 4096 bytes
LTFS20010D SCSI request: [ 08 02 00 10 00 00 ] Requested length=4096
LTFS20011D SCSI outcome: Driver status=0x00 SCSI status=0x02 Actual length=0
LTFS20012D SCSI sense  : F0 00 80 00 00 10 00 0A 00 00 00 00 00 01 00 00 00 00
LTFS20038D Read block: file mark detected
LTFS20061D Backend modesense: 0x00
LTFS20010D SCSI request: [ 5A 00 00 00 00 00 00 00 08 00 ] Requested length=8
LTFS20011D SCSI outcome: Driver status=0x00 SCSI status=0x00 Actual length=8
LTFS20010D SCSI request: [ 05 00 00 00 00 00 ] Requested length=6
LTFS20011D SCSI outcome: Driver status=0x00 SCSI status=0x00 Actual length=6
LTFS20057D Backend locate: (1, 0)
LTFS20010D SCSI request: [ 92 02 00 01 00 00 00 00 00 00 00 00 00 00 00 00 ] Requested length=0
LTFS20011D SCSI outcome: Driver status=0x00 SCSI status=0x00 Actual length=0
LTFS20010D SCSI request: [ 34 06 00 00 00 00 00 00 00 00 ] Requested length=32
LTFS20011D SCSI outcome: Driver status=0x00 SCSI status=0x00 Actual length=32
LTFS20060D Backend ReadPosition: Partition=1, LogObject=0, FMcount=0
LTFS20039D Backend read: 4096 bytes
LTFS20010D SCSI request: [ 08 02 00 10 00 00 ] Requested length=4096
LTFS20011D SCSI outcome: Driver status=0x00 SCSI status=0x00 Actual length=80
LTFS20039D Backend read: 4096 bytes
LTFS20010D SCSI request: [ 08 02 00 10 00 00 ] Requested length=4096
LTFS20011D SCSI outcome: Driver status=0x00 SCSI status=0x02 Actual length=0
LTFS20012D SCSI sense  : F0 00 80 00 00 10 00 0A 00 00 00 00 00 01 00 00 00 00
LTFS20038D Read block: file mark detected
LTFS20039D Backend read: 4096 bytes
LTFS20010D SCSI request: [ 08 02 00 10 00 00 ] Requested length=4096
LTFS20011D SCSI outcome: Driver status=0x00 SCSI status=0x00 Actual length=477
LTFS20039D Backend read: 4096 bytes
LTFS20010D SCSI request: [ 08 02 00 10 00 00 ] Requested length=4096
LTFS20011D SCSI outcome: Driver status=0x00 SCSI status=0x02 Actual length=0
LTFS20012D SCSI sense  : F0 00 80 00 00 10 00 0A 00 00 00 00 00 01 00 00 00 00
LTFS20038D Read block: file mark detected
LTFS20061D Backend modesense: 0x0F
LTFS20010D SCSI request: [ 5A 00 0F 00 00 00 00 00 20 00 ] Requested length=32
LTFS20011D SCSI outcome: Driver status=0x00 SCSI status=0x00 Actual length=32
LTFS20010D SCSI request: [ 55 10 00 00 00 00 00 00 20 00 ] Requested length=32
LTFS20011D SCSI outcome: Driver status=0x00 SCSI status=0x00 Actual length=32
LTFS20061D Backend modesense: 0x00
LTFS20010D SCSI request: [ 5A 00 00 00 00 00 00 00 08 00 ] Requested length=8
LTFS20011D SCSI outcome: Driver status=0x00 SCSI status=0x00 Actual length=8
LTFS20010D SCSI request: [ 05 00 00 00 00 00 ] Requested length=6
LTFS20011D SCSI outcome: Driver status=0x00 SCSI status=0x00 Actual length=6
LTFS11013D Partition labels are valid
LTFS11014D Reading MAM parameters
LTFS20061D Backend logsense: 0x17
LTFS20010D SCSI request: [ 4D 00 57 00 00 00 00 04 00 00 ] Requested length=1024
LTFS20011D SCSI outcome: Driver status=0x00 SCSI status=0x00 Actual length=172
LTFS20097D Drive firmware update needed to enable EOD status check
LTFS20061D Backend logsense: 0x17
LTFS20010D SCSI request: [ 4D 00 57 00 00 00 00 04 00 00 ] Requested length=1024
LTFS20011D SCSI outcome: Driver status=0x00 SCSI status=0x00 Actual length=172
LTFS20057D Backend readattr: (0, 2060)
LTFS20010D SCSI request: [ 8C 00 00 00 00 00 00 00 08 0C 00 00 00 4F 00 00 ] Requested length=79
LTFS20011D SCSI outcome: Driver status=0x00 SCSI status=0x00 Actual length=79
LTFS20057D Backend readattr: (1, 2060)
LTFS20010D SCSI request: [ 8C 00 00 00 00 00 00 01 08 0C 00 00 00 4F 00 00 ] Requested length=79
LTFS20011D SCSI outcome: Driver status=0x00 SCSI status=0x00 Actual length=79
LTFS20057D Backend readattr: (0, 9)
LTFS20010D SCSI request: [ 8C 00 00 00 00 00 00 00 00 09 00 00 00 0D 00 00 ] Requested length=13
LTFS20011D SCSI outcome: Driver status=0x00 SCSI status=0x00 Actual length=13
LTFS11018D Done reading MAM parameters
LTFS20057D Backend readattr: (0, 2048)
LTFS20010D SCSI request: [ 8C 00 00 00 00 00 00 00 08 00 00 00 00 18 00 00 ] Requested length=24
LTFS20011D SCSI outcome: Driver status=0x00 SCSI status=0x00 Actual length=24
LTFS20057D Backend readattr: (0, 2049)
LTFS20010D SCSI request: [ 8C 00 00 00 00 00 00 00 08 01 00 00 00 18 00 00 ] Requested length=24
LTFS20011D SCSI outcome: Driver status=0x00 SCSI status=0x00 Actual length=24
LTFS20057D Backend readattr: (0, 2050)
LTFS20010D SCSI request: [ 8C 00 00 00 00 00 00 00 08 02 00 00 00 18 00 00 ] Requested length=24
LTFS20011D SCSI outcome: Driver status=0x00 SCSI status=0x00 Actual length=24
LTFS20057D Backend readattr: (0, 2059)
LTFS20010D SCSI request: [ 8C 00 00 00 00 00 00 00 08 0B 00 00 00 18 00 00 ] Requested length=24
LTFS20011D SCSI outcome: Driver status=0x00 SCSI status=0x00 Actual length=24
LTFS20057D Backend readattr: (0, 2051)
LTFS20010D SCSI request: [ 8C 00 00 00 00 00 00 00 08 03 00 00 00 A9 00 00 ] Requested length=169
LTFS20011D SCSI outcome: Driver status=0x00 SCSI status=0x00 Actual length=169
LTFS17300D Done reading MAM attributes
LTFS11019D Checking volume consistency
LTFS20057D Backend locate: (0, 5)
LTFS20010D SCSI request: [ 92 02 00 00 00 00 00 00 00 00 00 05 00 00 00 00 ] Requested length=0
LTFS20011D SCSI outcome: Driver status=0x00 SCSI status=0x00 Actual length=0
LTFS20010D SCSI request: [ 34 06 00 00 00 00 00 00 00 00 ] Requested length=32
LTFS20011D SCSI outcome: Driver status=0x00 SCSI status=0x00 Actual length=32
LTFS20060D Backend ReadPosition: Partition=0, LogObject=5, FMcount=3
LTFS20039D Backend read: 524288 bytes
LTFS20010D SCSI request: [ 08 00 08 00 00 00 ] Requested length=524288
LTFS20011D SCSI outcome: Driver status=0x00 SCSI status=0x02 Actual length=946
LTFS20012D SCSI sense  : F0 00 20 00 07 FC 4E 0A 00 00 00 00 00 00 00 00 00 00
LTFS20039D Backend read: 524288 bytes
LTFS20010D SCSI request: [ 08 00 08 00 00 00 ] Requested length=524288
LTFS20011D SCSI outcome: Driver status=0x00 SCSI status=0x02 Actual length=0
LTFS20012D SCSI sense  : F0 00 80 00 08 00 00 0A 00 00 00 00 00 01 00 00 00 00
LTFS20038D Read block: file mark detected
LTFS20059D Backend space back file marks: 1
LTFS20010D SCSI request: [ 11 01 FF FF FF 00 ] Requested length=0
LTFS20011D SCSI outcome: Driver status=0x00 SCSI status=0x00 Actual length=0
LTFS20010D SCSI request: [ 34 06 00 00 00 00 00 00 00 00 ] Requested length=32
LTFS20011D SCSI outcome: Driver status=0x00 SCSI status=0x00 Actual length=32
LTFS20060D Backend ReadPosition: Partition=0, LogObject=6, FMcount=4
LTFS11197E Cannot read index: back pointer is corrupt
LTFS11024E Cannot mount volume: read index failed on the index partition
LTFS14013E Cannot mount the volume
LTFS12028D Unlocking medium
LTFS20010D SCSI request: [ 1E 00 00 00 00 00 ] Requested length=0
LTFS20011D SCSI outcome: Driver status=0x00 SCSI status=0x00 Actual length=0
LTFS20076I Triggering drive diagnostic dump
LTFS20010D SCSI request: [ A4 1F 0C 00 00 00 00 00 00 00 00 00 ] Requested length=0
LTFS20011D SCSI outcome: Driver status=0x00 SCSI status=0x02 Actual length=0
LTFS20012D SCSI sense  : 70 00 05 00 00 00 00 0A 00 00 00 00 20 00 00 00 00 00
LTFS20077W Unable to generate drive dump
LTFS20096I Diagnostic dump complete
LTFS20010D SCSI request: [ 00 00 00 00 00 00 ] Requested length=0
LTFS20011D SCSI outcome: Driver status=0x00 SCSI status=0x00 Actual length=0
LTFS20061D Backend modesense: 0x10
LTFS20010D SCSI request: [ 5A 00 10 01 00 00 00 00 30 00 ] Requested length=48
LTFS20011D SCSI outcome: Driver status=0x00 SCSI status=0x00 Actual length=48
LTFS20010D SCSI request: [ 55 10 00 00 00 00 00 00 30 00 ] Requested length=48
LTFS20011D SCSI outcome: Driver status=0x00 SCSI status=0x00 Actual length=48
LTFS12025D Releasing device
LTFS20010D SCSI request: [ 17 00 00 00 00 00 ] Requested length=0
LTFS20011D SCSI outcome: Driver status=0x00 SCSI status=0x00 Actual length=0
LTFS20010D SCSI request: [ 01 00 00 00 00 00 ] Requested length=0
LTFS20011D SCSI outcome: Driver status=0x00 SCSI status=0x00 Actual length=0
LTFS20010D SCSI request: [ 34 06 00 00 00 00 00 00 00 00 ] Requested length=32
LTFS20011D SCSI outcome: Driver status=0x00 SCSI status=0x00 Actual length=32
LTFS20060D Backend ReadPosition: Partition=0, LogObject=0, FMcount=0

Thanks!
Patrick

QUADStor VTL Support

unread,
Jul 26, 2013, 2:49:11 PM7/26/13
to quadstor-vtl
Works  fine here both with the current code and 2.2.8 package with both HP LTO 5 and LTO 6. Further below are messages from our test which is similar to yours except that there are no errors.

Have you by any chance specified a maximum vcartridge size in quadstor.conf ? That is currently not supported with LTFS. But with that formatting should have failed.

We remember a similar issue when LTFS support was being developed. Is this problem consistent ? That is can you try deleting the vcartridge and try again. Also try with LTO 6.

Kindly also send the /var/log/messages file (off list). Maybe any errors are logged there.

Is the virtual tape drive on the same machine as /dev/st4 or connected via iSCSI/FC ?


[root@kvm1 x86_64]# /etc/rc.d/init.d/quadstorvtl start
Starting iSCSI target service:                             [  OK  ]
[root@kvm1 x86_64]# /usr/local/bin/mkltfs -d /dev/st0

LTFS15000I Starting mkltfs, LTFS version 2.1.0, log level 2
LTFS15041I Launched by "/usr/local/bin/mkltfs -d /dev/st0"

LTFS15042I This binary is built for Linux (x86_64)
LTFS15043I GCC version is 4.1.2 20080704 (Red Hat 4.1.2-48)
LTFS17087I Kernel version: Linux version 2.6.32-220.el6.x86_64 (mock...@c6b18n3.bsys.dev.centos.org) (gcc version 4.4.6 20110731 (Red Hat 4.4.6-3) (GCC) ) #1 SMP Tue Dec 6 19:48:22 GMT 2011 x86_64
LTFS17089I Distribution: CentOS release 6.2 (Final)
LTFS17089I Distribution: CentOS release 6.2 (Final)
LTFS17089I Distribution: CentOS release 6.2 (Final)
LTFS15003I Formatting device '/dev/st0'

LTFS15004I LTFS volume blocksize: 524288
LTFS15005I Index partition placement policy: None

LTFS17085I Plugin: Loading "ltotape" driver
LTFS20013I Drive type is HP LTO5, serial number is QDRS000000
LTFS17160I Maximum device block size is 524288
LTFS15049I Checking the medium
LTFS15010I Creating data partition b on SCSI partition 1
LTFS15011I Creating index partition a on SCSI partition 0
LTFS17165I Resetting the medium's capacity proportion
LTFS11097I Partitioning the medium
LTFS11100I Writing label to partition b
LTFS11278I Writing index to partition b
LTFS11100I Writing label to partition a
LTFS11278I Writing index to partition a
LTFS15013I Volume UUID is: e31a7380-3c84-4497-ac83-f22fffc17591


LTFS15019I Volume capacity is 1473 GB
LTFS20076I Triggering drive diagnostic dump
LTFS20077W Unable to generate drive dump
LTFS20096I Diagnostic dump complete
LTFS15024I Medium formatted successfully
[root@kvm1 x86_64]# /usr/local/bin/ltfs /mnt-ltfs -o devname=/dev/st0

LTFS14000I LTFS starting, LTFS version 2.1.0, log level 2
LTFS14058I LTFS Format Specification version 2.1.0
LTFS14104I Launched by "/usr/local/bin/ltfs /mnt-ltfs -o devname=/dev/st0"

LTFS14105I This binary is built for Linux (x86_64)
LTFS14106I GCC version is 4.1.2 20080704 (Red Hat 4.1.2-48)
LTFS17087I Kernel version: Linux version 2.6.32-220.el6.x86_64 (mock...@c6b18n3.bsys.dev.centos.org) (gcc version 4.4.6 20110731 (Red Hat 4.4.6-3) (GCC) ) #1 SMP Tue Dec 6 19:48:22 GMT 2011 x86_64
LTFS17089I Distribution: CentOS release 6.2 (Final)
LTFS17089I Distribution: CentOS release 6.2 (Final)
LTFS17089I Distribution: CentOS release 6.2 (Final)

LTFS14063I Sync type is "time", Sync time is 300 sec
LTFS17085I Plugin: Loading "ltotape" driver
LTFS17085I Plugin: Loading "unified" iosched
LTFS20013I Drive type is HP LTO5, serial number is QDRS000000
LTFS17160I Maximum device block size is 524288
LTFS11005I Mounting the volume
LTFS14111I Initial setup completed successfully
LTFS14112I Invoke 'mount' command to check the result of final setup
LTFS14113I Specified mount point is listed if succeeded

[root@kvm1 x86_64]# df
Filesystem           1K-blocks      Used Available Use% Mounted on
/dev/mapper/vg_kvm1-lv_root
                      38744716  13329168  23447420  37% /
tmpfs                   768388         0    768388   0% /dev/shm
/dev/vda1               495844     23524    446720   6% /boot
ltfs:/dev/st0        1438089216    131072 1437958144   1% /mnt-ltfs




 

Message has been deleted

Patrick Dung

unread,
Jul 27, 2013, 12:59:15 PM7/27/13
to quadst...@googlegroups.com
1. I use the default vcartidge size.
2. I have tried to do a fresh install of quadstor-vtl 2.2.8  on rhel 6.3 x64.
I selected HP LTO5 as the vtape. But still have the same issue.
By the way, I am using the default Linux tape device driver. I have not installed the HP's Linux tape device driver.
I do all the test on the same server without iscsi.

I will send the log off list.

QUADStor VTL Support

unread,
Jul 27, 2013, 3:48:01 PM7/27/13
to quadst...@googlegroups.com
Still no luck in reproducing this. Works every time. Looking back at
your original post, we dont seem to get the following messages.

LTFS11175E Cannot read ANSI label: expected 80 bytes, but received 4096
LTFS11009E Cannot read volume: failed to read partition labels.

It seems that in your first test the tape already had a partition 1 or
atleast mkltfs thinks so.
Could you try out the following in your setup.
1. Create a new blank vcartridge, and load that into the drive
2. mkltfs -o trace
3. ltfs -o trace

Now then delete the vcartridge.

mt -f <device path> compression 0
Repeat 1 - 3 and send us the logs for all the operations. That should
help us debug this better

Patrick Dung

unread,
Jul 28, 2013, 11:18:35 AM7/28/13
to quadst...@googlegroups.com
Hi quadstor,

It seems turning off the compression looks good.

Please see the attached file.

Thanks,
Patrick
hp lto5 test ltfs.txt

QUADStor VTL Support

unread,
Jul 30, 2013, 7:05:23 AM7/30/13
to quadst...@googlegroups.com
This should be fixed in 2.2.9. Although we were unable to reproduce
this, based on your logs, we believe that the fix has gone into this
release. Please try with the new release.
> --
> You received this message because you are subscribed to the Google Groups
> "QUADStor VTL" group.
> To unsubscribe from this group and stop receiving emails from it, send an
> email to quadstor-vtl...@googlegroups.com.
> For more options, visit https://groups.google.com/groups/opt_out.
>
>
>

Patrick Dung

unread,
Jul 30, 2013, 12:19:03 PM7/30/13
to quadst...@googlegroups.com
Yes, I don't have problem with the new release, thanks!
Reply all
Reply to author
Forward
0 new messages