Quantcast

mhVTL 1.5-4 exporting via FC to a AS400

classic Classic list List threaded Threaded
58 messages Options
123
npf
Reply | Threaded
Open this post in threaded view
|  
Report Content as Inappropriate

mhVTL 1.5-4 exporting via FC to a AS400

npf
Hello,

I'm trying to export a VTL to an AS400 server via FC. I'm using mhvtl 1.5-4 in a centos 7 server with 3.10.0-327.10.1.el7.scst.x86_64 kernel. Here is my device.conf:

VERSION: 5

Library: 90 CHANNEL: 13 TARGET: 00 LUN: 00
 Vendor identification: IBM
 Product identification: 3573-TL
 Product revision level: 4.02
 Unit serial number: 70000090
 NAA: 90:11:22:33:ab:7:00:00
 Home directory: /opt/mhvtl/90
 Backoff: 400

Drive: 91 CHANNEL: 14 TARGET: 00 LUN: 00
 Library ID: 90 Slot: 01
 Vendor identification: IBM
 Product identification: ULT3580-TD4
 Product revision level: 252D
 Unit serial number: 70000091
 NAA: 90:11:22:33:ab:7:00:01
 Compression: factor 1 enabled 0
 Compression type: lzo
 Backoff: 400

And here is my library contents:
Drive1:
 
MAP 1:
 
Picker 1:
 
Slot 1: M00001L3
Slot 2: M00002L3
Slot 3: M00003L3
Slot 4: M00004L3
Slot 5:
Slot 6:

The devices appear ok:

[root@vtl ~]# lsscsi -g
[0:0:0:0]    disk    DGC      LUNZ             0430  /dev/sda   /dev/sg1
[0:0:1:0]    disk    DGC      LUNZ             0430  /dev/sdb   /dev/sg2
[1:0:0:0]    cd/dvd  HL-DT-ST DVD-ROM GDR8084N 3.00  /dev/sr0   /dev/sg0
[4:13:0:0]   mediumx IBM      3573-TL          4.02  /dev/sch0  /dev/sg4
[4:14:0:0]   tape    IBM      ULT3580-TD4      252D  /dev/st0   /dev/sg3

Here are my scst.conf file:

HANDLER dev_changer {
        DEVICE 4:13:0:0
}

HANDLER dev_tape {
        DEVICE 4:14:0:0
}

TARGET_DRIVER qla2x00t {
        enabled 1

        TARGET 21:00:00:1b:32:1a:76:c7 {
                GROUP BRG-P7-PORT1 {
                        INITIATOR 10:00:00:00:c9:f6:00:c7
                        LUN 0 4:13:0:0
                        LUN 1 4:14:0:0
                }
                GROUP BRG-P7-PORT2 {
                        INITIATOR 10:00:00:00:c9:f6:00:c8
                        LUN 0 dummy
                }
                enabled 1
        }

        TARGET 21:01:00:1b:32:3a:76:c7 {
                enabled 0
        }
}

Everything works fine if the FC initiator is a linux server. I can do load tapes, do backups, etc.
If the initiator is a AS400 server (with the latest OS and PTFs (hotfixes)) i sometimes see the library and tape and other times i don't. It takes about 3 minutes to make the library online in AS400 and i'm uname to load tapes and format them.

Please find the mhvtl verbose=3 logs in http://pastebin.com/PCx4Ya0A

Any ideas on how to make it work? Thanks,
Nuno Fernandes
npf
Reply | Threaded
Open this post in threaded view
|  
Report Content as Inappropriate

Re: mhVTL 1.5-4 exporting via FC to a AS400

npf
Hello,

I've kept on trying and narrowing it down. I've tried to present only the tape drive to the as400 server and loading tapes from the linux box.

I can make the drive online in the as400 box. But when i try to format a tape with the following parameters:

INZTAP DEV(TAP16) NEWVOL(N00001) CHECK(*NO) DENSITY(*CTGTYPE)

It blocks in the AS400 command. In the mhvtl i get the logs:

http://pastebin.com/9d4irk7e

After 5 minutes i get an error on the AS400 box and the following logs on the mhvtl:

Apr 12 16:20:34 vtl kernel: qla2x00t(9): task abort (s_id=d6:2a:0, tag=-1, param=0)
Apr 12 16:20:34 vtl vtltape[5646]: CDB (1672) (delay 488005): 4d 00 4c 00 00 00 00 01 00 00
Apr 12 16:20:34 vtl vtltape[5646]: ssc_log_sense(): LOG SENSE (1672) ** :  Sequential Access Device Log page
Apr 12 16:20:34 vtl vtltape[5646]: lookup_log_pg(): Looking for: log page 0x0c
Apr 12 16:20:34 vtl vtltape[5646]: lookup_log_pg(): Sequential Access (0x0c)
Apr 12 16:20:34 vtl vtltape[5646]: completeSCSICommand(): OP s/n: (1672), sz: 128, sam_status: 0

Thanks for any help.

Nuno Fernandes
npf
Reply | Threaded
Open this post in threaded view
|  
Report Content as Inappropriate

Re: mhVTL 1.5-4 exporting via FC to a AS400

npf
In reply to this post by npf
Forgot to mention the configuration as of now:

Device.conf:

VERSION: 5

Library: 50 CHANNEL: 1 TARGET: 00 LUN: 00
 Vendor identification: IBM
 Product identification: 3573-TL
 Product revision level: 4.02
 Unit serial number: 70000050
 NAA: 50:11:22:33:ab:1:00:00
 Home directory: /opt/mhvtl/50
 Backoff: 400

Drive: 51 CHANNEL: 1 TARGET: 00 LUN: 01
 Library ID: 50 Slot: 01
 Vendor identification: IBM
 Product identification: ULT3580-TD4
 Product revision level: 252D
 Unit serial number: 70000051
 NAA: 50:11:22:33:ab:1:00:01
 Compression: factor 1 enabled 0
 Compression type: lzo
 Backoff: 400

Librarycontents:
[root@vtl ~]# cat /etc/mhvtl/library_contents.50
 
Drive1:
 
MAP 1:
MAP 2:
MAP 3:
MAP 4:
 
Picker 1:
 
Slot 1: N00001L4
Slot 2:
Slot 3:
Slot 4:
Slot 5:
Slot 6:
Slot 7:
Slot 8:
Slot 9:
Slot 10:
Slot 11:
Slot 12:
Slot 13:
Slot 14:
Slot 15:
Slot 16:
Slot 17:
Slot 18:
Slot 19:
Slot 20:

[root@vtl ~]# cat /etc/scst.conf
HANDLER dev_tape {
        DEVICE 4:1:0:1
}

TARGET_DRIVER qla2x00t {
        enabled 1

        TARGET 21:00:00:1b:32:1a:76:c7 {
                GROUP BRG-P7-PORT1 {
                        INITIATOR 10:00:00:00:c9:f6:00:c7
                        LUN 0 4:1:0:1
                }
                GROUP BRG-P7-PORT2 {
                        INITIATOR 10:00:00:00:c9:f6:00:c8
                        LUN 0 dummy
                }
                enabled 1
        }

        TARGET 21:01:00:1b:32:3a:76:c7 {
                enabled 0
        }
}

[root@vtl ~]# lsscsi -g
[1:0:0:0]    cd/dvd  HL-DT-ST DVD-ROM GDR8084N 3.00  /dev/sr0   /dev/sg0
[4:1:0:0]    mediumx IBM      3573-TL          4.02  /dev/sch0  /dev/sg2
[4:1:0:1]    tape    IBM      ULT3580-TD4      252D  /dev/st0   /dev/sg1
Reply | Threaded
Open this post in threaded view
|  
Report Content as Inappropriate

Re: mhVTL 1.5-4 exporting via FC to a AS400

Mark Harvey
Administrator
Sorry for the extra long time between posting and this response.

Having a 'quick' look over the information in the syslog (/var/log/messages) - I see the following sequence of events:

$ egrep "complete|\*\*" mhvtl_fc_as400.txt
Apr 12 16:15:36 vtl vtltape[5646]: ssc_tur(): Test Unit Ready (1657) ** : Yes
Apr 12 16:15:36 vtl vtltape[5646]: completeSCSICommand(): OP s/n: (1657), sz: 0, sam_status: 0
Apr 12 16:15:36 vtl vtltape[5646]: spc_mode_sense(): MODE SENSE 10 (1658) **
Apr 12 16:15:36 vtl vtltape[5646]: completeSCSICommand(): OP s/n: (1658), sz: 214, sam_status: 0
Apr 12 16:15:36 vtl vtltape[5646]: ssc_read_position(): READ POSITION (1659) **
Apr 12 16:15:36 vtl vtltape[5646]: completeSCSICommand(): OP s/n: (1659), sz: 20, sam_status: 0
Apr 12 16:15:36 vtl vtltape[5646]: ssc_tur(): Test Unit Ready (1660) ** : Yes
Apr 12 16:15:36 vtl vtltape[5646]: completeSCSICommand(): OP s/n: (1660), sz: 0, sam_status: 0
Apr 12 16:15:36 vtl vtltape[5646]: spc_mode_sense(): MODE SENSE 10 (1661) **
Apr 12 16:15:36 vtl vtltape[5646]: completeSCSICommand(): OP s/n: (1661), sz: 32, sam_status: 0
Apr 12 16:15:36 vtl vtltape[5646]: ssc_report_density_support(): REPORT MOUNTED MEDIA DENSITY SUPPORT (1662) **
Apr 12 16:15:36 vtl vtltape[5646]: completeSCSICommand(): OP s/n: (1662), sz: 56, sam_status: 0
Apr 12 16:15:36 vtl vtltape[5646]: spc_mode_sense(): MODE SENSE 10 (1663) **
Apr 12 16:15:36 vtl vtltape[5646]: completeSCSICommand(): OP s/n: (1663), sz: 40, sam_status: 0
Apr 12 16:15:36 vtl vtltape[5646]: ssc_tur(): Test Unit Ready (1664) ** : Yes
Apr 12 16:15:36 vtl vtltape[5646]: completeSCSICommand(): OP s/n: (1664), sz: 0, sam_status: 0
Apr 12 16:15:36 vtl vtltape[5646]: spc_mode_sense(): MODE SENSE 10 (1665) **
Apr 12 16:15:36 vtl vtltape[5646]: completeSCSICommand(): OP s/n: (1665), sz: 214, sam_status: 0
Apr 12 16:15:36 vtl vtltape[5646]: ssc_read_position(): READ POSITION (1666) **
Apr 12 16:15:36 vtl vtltape[5646]: completeSCSICommand(): OP s/n: (1666), sz: 20, sam_status: 0
Apr 12 16:15:36 vtl vtltape[5646]: ssc_tur(): Test Unit Ready (1667) ** : Yes
Apr 12 16:15:36 vtl vtltape[5646]: completeSCSICommand(): OP s/n: (1667), sz: 0, sam_status: 0
Apr 12 16:15:36 vtl vtltape[5646]: spc_mode_sense(): MODE SENSE 10 (1668) **
Apr 12 16:15:36 vtl vtltape[5646]: completeSCSICommand(): OP s/n: (1668), sz: 32, sam_status: 0
Apr 12 16:15:36 vtl vtltape[5646]: ssc_report_density_support(): REPORT MOUNTED MEDIA DENSITY SUPPORT (1669) **
Apr 12 16:15:36 vtl vtltape[5646]: completeSCSICommand(): OP s/n: (1669), sz: 56, sam_status: 0
Apr 12 16:15:36 vtl vtltape[5646]: spc_mode_sense(): MODE SENSE 10 (1670) **
Apr 12 16:15:36 vtl vtltape[5646]: completeSCSICommand(): OP s/n: (1670), sz: 40, sam_status: 0
Apr 12 16:15:36 vtl vtltape[5646]: ssc_rewind(): REWINDING (1671) **
Apr 12 16:15:37 vtl vtltape[5646]: completeSCSICommand(): OP s/n: (1671), sz: 0, sam_status: 0

All SCSI commands sent to the vtl have been correctly completed (i.e. SAM Status '0' returned).

After 5 minutes i get an error on the AS400 box and the following logs on the mhvtl:

Apr 12 16:20:34 vtl kernel: qla2x00t(9): task abort (s_id=d6:2a:0, tag=-1, param=0)

Apr 12 16:20:34 vtl vtltape[5646]: CDB (1672) (delay 488005): 4d 00 4c 00 00 00 00 01 00 00
Apr 12 16:20:34 vtl vtltape[5646]: ssc_log_sense(): LOG SENSE (1672) ** :  Sequential Access Device Log page
Apr 12 16:20:34 vtl vtltape[5646]: lookup_log_pg(): Looking for: log page 0x0c
Apr 12 16:20:34 vtl vtltape[5646]: lookup_log_pg(): Sequential Access (0x0c)
Apr 12 16:20:34 vtl vtltape[5646]: completeSCSICommand(): OP s/n: (1672), sz: 128, sam_status: 0
The sudden appearance of the 'qla2x00t(9)' task abort..
Then commands are being received and processed by the vtl again.

I have a feeling, it's not the vtl that's causing the hic-up but the SCST.. It's unable to process something, and eventually times out after 5 minutes - with the task abort.
I've not had much experience with SCST - sorry, I can't really offer any suggestions on troubleshooting that.
Most of my use-cases are content with iSCSI and the STGT suits my purposes..

If you can enable logging within the SCST stack, I'd be happy to pass a second set of eyes over it - but can't promise anything.
Regards from Australia
Mark Harvey
npf
Reply | Threaded
Open this post in threaded view
|  
Report Content as Inappropriate

Re: mhVTL 1.5-4 exporting via FC to a AS400

npf
In reply to this post by npf
Hello,

I've increased the log level on the qla driver:
# cat /etc/modprobe.d/scst.conf
options qla2xxx_scst qlini_mode=disabled ql2xextended_error_logging=0x7fffffff

And get a lot of information. I tried againt to format a tape and i get in the logs a

sam_status: 2

Please find the log in http://pastebin.com/3HzLJTJ6

Hope it helps..

Best regards,
Nuno Fernandes
Reply | Threaded
Open this post in threaded view
|  
Report Content as Inappropriate

Re: mhVTL 1.5-4 exporting via FC to a AS400

Mark Harvey
Administrator
First thing I see in the logs is:

May  2 18:20:49 vtl vtltape[3088]: CDB (1453) (delay 157605): 00 00 00 00 00 00
May  2 18:20:49 vtl vtltape[3088]: return_sense(): [Key/ASC/ASCQ] [02 3a 00]
May  2 18:20:49 vtl vtltape[3088]: ssc_tur(): Test Unit Ready (1453) ** : No, No tape loaded
May  2 18:20:49 vtl vtltape[3088]: completeSCSICommand(): s/n: (1453), sz: 0, sam_status: 2 [02 3a 00]
i.e. There is no tape in the tape drive..

Then I see several MODE SENSE commands - ok, tape doesn't need to be loaded for this to work.

Then I see the following attempted:
May  2 18:20:49 vtl vtltape[3088]: CDB (1455) (delay 5): 34 00 00 00 00 00 00 00 00 00
May  2 18:20:49 vtl vtltape[3088]: ssc_read_position(): READ POSITION (1455) **
May  2 18:20:49 vtl vtltape[3088]: ssc_read_position(): service_action: 0
May  2 18:20:49 vtl vtltape[3088]: return_sense(): [Key/ASC/ASCQ] [02 3a 00]
May  2 18:20:49 vtl vtltape[3088]: completeSCSICommand(): s/n: (1455), sz: 0, sam_status: 2 [02 3a 00]
May  2 18:20:49 vtl vtltape[3088]: CDB (1456) (delay 1205): 01 00 00 00 00 00
May  2 18:20:49 vtl vtltape[3088]: ssc_rewind(): REWINDING (1456) **
May  2 18:20:49 vtl vtltape[3088]: return_sense(): [Key/ASC/ASCQ] [02 3a 00]
May  2 18:20:49 vtl vtltape[3088]: completeSCSICommand(): s/n: (1456), sz: 0, sam_status: 2 [02 3a 00]
i.e. Read position.. We've already returned to the OS / Application that there is no tape in the tape drive via the Test Unit Ready (TUR) command. Yet it's persisting to identify where in the tape it is positioned.
Then it attempts to rewind the tape..

SAM Status 2 with ASC/ASCQ of 3a/00 is a 'MEDIUM NOT PRESENT' - i.e. there is no medium loaded.
Regards from Australia
Mark Harvey
npf
Reply | Threaded
Open this post in threaded view
|  
Report Content as Inappropriate

Re: mhVTL 1.5-4 exporting via FC to a AS400

npf
In reply to this post by npf
Hello,

You are correct. When i did an tape "offline" in the AS400, it ejected the tape from the drive. I've mtx unload and load again and the error is now different.

In the as400 i get "Wrong type of cartridge in device TAP19" when i'm trying to format it. The mhvtl logs are in http://pastebin.com/yPPHjysD but i don't see any errors in there (sam_status is always 0). I think is something that as400 doesn't like in the tape information.

I have a vtl (closed source) that works and i could do some comparing using sginfo or mt -f /dev/st0 status, or any other command you would like me to test. Do you have any recomendations?

Thanks,
Nuno Fernandes
Reply | Threaded
Open this post in threaded view
|  
Report Content as Inappropriate

Re: mhVTL 1.5-4 exporting via FC to a AS400

Mark Harvey
Administrator
Re: VTL that works
Many thanks for the offer. 

I'll extract the scsi commands and provide a sg_raw wrapper around it. Won't be until tomorrow at earliest. 

Mean while I'll review the current logs and see if anything stands out.

Thanks for sticking with this. I would like to see it work. 

Sent from my autocorrecting iPhone

On 3 May 2016, at 18:35, npf [via mhVTL - A Linux Virtual Tape Library] <[hidden email]> wrote:

Hello,

You are correct. When i did an tape "offline" in the AS400, it ejected the tape from the drive. I've mtx unload and load again and the error is now different.

In the as400 i get "Wrong type of cartridge in device TAP19" when i'm trying to format it. The mhvtl logs are in http://pastebin.com/yPPHjysD but i don't see any errors in there (sam_status is always 0). I think is something that as400 doesn't like in the tape information.

I have a vtl (closed source) that works and i could do some comparing using sginfo or mt -f /dev/st0 status, or any other command you would like me to test. Do you have any recomendations?

Thanks,
Nuno Fernandes


To start a new topic under mhVTL - A Linux Virtual Tape Library, email [hidden email]
To unsubscribe from mhVTL - A Linux Virtual Tape Library, click here.
NAML
Regards from Australia
Mark Harvey
Reply | Threaded
Open this post in threaded view
|  
Report Content as Inappropriate

Re: mhVTL 1.5-4 exporting via FC to a AS400

Mark Harvey
Administrator
Actually, the wrapper is simpler than I thought..

Can you cut/past below into a file and execute the file -> Need to change 'DEV=/dev/sg??' to suit your device path...

#!/bin/bash

DEV=/dev/sg6
S="/usr/bin/sg_raw -r 10k $DEV"

$S 00 00 00 00 00 00
$S 5a 08 3f 00 00 00 00 00 ff 00
$S 34 00 00 00 00 00 00 00 00 00
$S 00 00 00 00 00 00
$S 5a 00 10 00 00 00 00 10 00 00
$S 44 01 00 00 00 00 00 10 00 00
$S 5a 08 1d 00 00 00 00 10 00 00
$S 01 00 00 00 00 00
$S 4d 00 4c 00 00 00 00 01 00 00
$S 00 00 00 00 00 00
$S 5a 08 3f 00 00 00 00 00 ff 00
$S 34 00 00 00 00 00 00 00 00 00
$S 00 00 00 00 00 00
$S 5a 00 10 00 00 00 00 10 00 00
$S 44 01 00 00 00 00 00 10 00 00
$S 5a 08 1d 00 00 00 00 10 00 00
$S 01 00 00 00 00 00
$S 4d 00 4c 00 00 00 00 01 00 00
Regards from Australia
Mark Harvey
npf
Reply | Threaded
Open this post in threaded view
|  
Report Content as Inappropriate

Re: mhVTL 1.5-4 exporting via FC to a AS400

npf
In reply to this post by npf
Hello,

Please find the output of the script:

using MHVTL - http://pastebin.com/vCZCGVxN

using closed source VTL - http://pastebin.com/5vRGSNjM

Hope it helps,

Best regards,
Nuno Fernandes
Reply | Threaded
Open this post in threaded view
|  
Report Content as Inappropriate

Re: mhVTL 1.5-4 exporting via FC to a AS400

Mark Harvey
Administrator
In reply to this post by Mark Harvey
When I try and format it
You wouldn't happen to be trying to use LTFS at all ?

LTFS is currently not supported. I'm working on a new back-end tape format which will allow this flexibility. Unfortunately, the supply of spare time to do this is a little short.

I've found a couple of short comings with the MODE pages anyway. The fixes are in the works.
Regards from Australia
Mark Harvey
npf
Reply | Threaded
Open this post in threaded view
|  
Report Content as Inappropriate

Re: mhVTL 1.5-4 exporting via FC to a AS400

npf
Hello,

Not to my knowledge.. I'm using the inztap command on the AS400. Reading from https://www.ibm.com/support/knowledgecenter/ssw_i5_54/cl/inztap.htm i can see that:

"The Initialize Tape (INZTAP) command is used to initialize magnetic tapes for use on the system. This command is used to initialize a tape with a standard volume label for standard label magnetic tape processing, or to initialize a tape with no labels for unlabeled magnetic tape processing."

I don't find anything related to LTFS.

The real command is:
inztap dev(tap19) newvol(n00001) newownid(*BLANK) CHECK(*NO) DENSITY(*DEVTYPE)

P.S. - Besides, LTFS is not supported on LTO4. Only in LTO5 and afterwards.

Best regards,
Nuno Fernandes
npf
Reply | Threaded
Open this post in threaded view
|  
Report Content as Inappropriate

Re: mhVTL 1.5-4 exporting via FC to a AS400

npf
In reply to this post by npf
Hello,

Any news on the logs? Is there any test that you would like me to do?

Thanks
Nuno Fernandes
Reply | Threaded
Open this post in threaded view
|  
Report Content as Inappropriate

Re: mhVTL 1.5-4 exporting via FC to a AS400

Mark Harvey
Administrator
I haven't forgotten...

I've made a start but unfortunately paid work stuff keeps getting in the way.

Hoping things settle down a little next week.

Sent from my iPad

On May 10, 2016, at 20:13, npf [via mhVTL - A Linux Virtual Tape Library] <[hidden email]> wrote:

Hello,

Any news on the logs? Is there any test that you would like me to do?

Thanks
Nuno Fernandes


To start a new topic under mhVTL - A Linux Virtual Tape Library, email [hidden email]
To unsubscribe from mhVTL - A Linux Virtual Tape Library, click here.
NAML
Regards from Australia
Mark Harvey
npf
Reply | Threaded
Open this post in threaded view
|  
Report Content as Inappropriate

Re: mhVTL 1.5-4 exporting via FC to a AS400

npf
In reply to this post by npf
Hello,

Did you have any time to see this? Is there anything i can do to help?

Thanks,
Best regards,
Nuno Fernandes
npf
Reply | Threaded
Open this post in threaded view
|  
Report Content as Inappropriate

Re: mhVTL 1.5-4 exporting via FC to a AS400

npf
In reply to this post by npf
Hello again,

Did you have any time to see this?

Thanks for any help,
Nuno Fernandes
Reply | Threaded
Open this post in threaded view
|  
Report Content as Inappropriate

Re: mhVTL 1.5-4 exporting via FC to a AS400

Mark Harvey
Administrator
Apologies. I thought I'd responded earlier. I've got a couple of patches to test and I'll send through in next day or so

Sent from my autocorrecting iPhone

On 24 Jun 2016, at 21:59, npf [via mhVTL - A Linux Virtual Tape Library] <[hidden email]> wrote:

Hello again,

Did you have any time to see this?

Thanks for any help,
Nuno Fernandes


To start a new topic under mhVTL - A Linux Virtual Tape Library, email [hidden email]
To unsubscribe from mhVTL - A Linux Virtual Tape Library, click here.
NAML
Regards from Australia
Mark Harvey
npf
Reply | Threaded
Open this post in threaded view
|  
Report Content as Inappropriate

Re: mhVTL 1.5-4 exporting via FC to a AS400

npf
In reply to this post by npf
Hello,

Can you please send us the patches so that we can test it?

Thanks,
Nuno Fernandes
Reply | Threaded
Open this post in threaded view
|  
Report Content as Inappropriate

Re: mhVTL 1.5-4 exporting via FC to a AS400

Mark Harvey
Administrator
So sorry.. I've been a little tied up over the last few weeks. Hopefully this is out of the way and I'll be much more responsive.

Attached are the two patches.
- One is to correct the size of the Disconnect / Reconnect mode page.
- 2nd patch updates the Medium Partition mode page to reflect the IBM LTO documentation. This should really be in the IBM personality module - but having the IBM default values are better than what was there. So this updates the default values.

0001-Correct-size-of-Disconnect-Reconnect-mode-page.patch
0002-Update-Medium-Partition-mode-page-to-suit-IBM-LTO5-d.patch

Please let me know how you get on.
Regards from Australia
Mark Harvey
npf
Reply | Threaded
Open this post in threaded view
|  
Report Content as Inappropriate

Re: mhVTL 1.5-4 exporting via FC to a AS400

npf
In reply to this post by npf
Hello,

I do see some great improvements :)

When i was trying to "activate" the drive it would have to wait 5 minutes and eventually i would get

vtl kernel: qla2x00t(9): task abort

Now this doesn't happen anymore. The drive activates immediately and deactivates immediately also.
Nevertheless when i try to format/initialize the tape, the as400 box reports:

"Wrong type of cartridge in device TAP23"

Tried with an emulated LTO3 and LTO4 tape. Please find the logs in http://pastebin.com/GcZrkwMq
Should i do a new test using your sg_raw script?

Thanks for your help.

Best regards,
Nuno Fernandes
123
Loading...