RFC: REPORT DENSITY rework.. (TSM LTO4 - LTO5 support)

classic Classic list List threaded Threaded
7 messages Options
Reply | Threaded
Open this post in threaded view
|  
Report Content as Inappropriate
star

RFC: REPORT DENSITY rework.. (TSM LTO4 - LTO5 support)

Mark Harvey
This post was updated on .
I'm in the middle of a major re-work of media handling and before going much further would like a sanity check by those TSM users out there.

As discussed / reported several times, TSM only works with Ultrium-1 media.

Background:
The 'report density' op code was of limited value and only returned 'lto-1' density.

This patch implements drive density - rather than previous media density.

I've commented out the 'media density' handling at the moment - That still needs to be reworked to suit the new drive density code.

Request for testing:
Apply this patch.
Configure non-lto-1 drive & media.
Test TSM for backup & restore functionality

The drive density support is a generic rule of :
 - "current version and one version back -> read/write support"
 - "Two versions back -> read only support"
e.g.
LTO4 will report LTO4 & LTO3 media as 'read/write', LTO2 as 'read-only'
AIT4 will report AIT4 and AIT3 media as read/write and AIT2 as read-only

Not tested - WORM support or Encryption. This handling needs to be reviewed with the changes implemented with this patch.

Patch available: 0001-SSC-Rework-report-density-op-code.patch

disclaimer: Only basic (one backup & verify) testing with NetBackup.

Reply | Threaded
Open this post in threaded view
|  
Report Content as Inappropriate
star

Re: RFC: REPORT DENSITY rework.. (TSM LTO4 - LTO5 support ?)

Mark Harvey
OK, bug number #1..
# dump_tape -f E01001L4 | less
PCL is : E01001L4
Media density code: 0x46
Media type code   : 0x08
Media description : Ultrium 4/16T
Tape Capacity     : 34359738368000
Remaining Tape Capacity : 34359738367924
Total num of filemarks: 1
Hdr:   Compressed data(0b), sz     76/1024  , Blk No.: 0, data 0
Hdr:         Filemark(03), sz             0, Blk No.: 1, data 76
Hdr:   Compressed data(0b), sz    126/1024  , Blk No.: 2, data 76
Hdr:   Compressed data(0b), sz  27616/65536 , Blk No.: 3, data 202

Manage to munged the 'Taoe Capacity' values..
nia
Reply | Threaded
Open this post in threaded view
|  
Report Content as Inappropriate
star

Re: RFC: REPORT DENSITY rework.. (TSM LTO4 - LTO5 support ?)

nia
Administrator
Mark Harvey wrote
OK, bug number #1..
# dump_tape -f E01001L4 | less
Manage to munged the 'Taoe Capacity' values..
Mark,

Shall we hold off on testing this patch with TSM ?

-nia
nia
Reply | Threaded
Open this post in threaded view
|  
Report Content as Inappropriate
star

Re: RFC: REPORT DENSITY rework.. (TSM LTO4 - LTO5 support ?)

nia
Administrator
nia wrote
Shall we hold off on testing this patch with TSM ?
I have tested quickly anyway .. I used LTO-5. Tested basic backup & Restore

This patch appears to have fixed the issue we had seen before in TSM ..

My configuration:

Library: 30 CHANNEL: 1 TARGET: 00 LUN: 00
 Vendor identification: IBM
 Product identification: 03584L22
 Product revision level: 4.02
 Unit serial number: 70000030
 NAA: 30:11:22:33:ab:1:00:00

Drive: 31 CHANNEL: 1 TARGET: 00 LUN: 01
 Library ID: 30 Slot: 01
 Vendor identification: IBM
 Product identification: ULT3580-TD5
 Product revision level: 252D
 Unit serial number: 70000031
 NAA: 30:11:22:33:ab:1:00:01
 Compression: factor 1 enabled 1

Drive: 32 CHANNEL: 1 TARGET: 00 LUN: 2
 Library ID: 30 Slot: 2
 Vendor identification: IBM
 Product identification: ULT3580-TD5
 Product revision level: 252D
 Unit serial number: 70000032
 NAA: 30:11:22:33:ab:1:00:2
 Compression: factor 1 enabled 1

Drive: 33 CHANNEL: 1 TARGET: 00 LUN: 3
 Library ID: 30 Slot: 3
 Vendor identification: IBM
 Product identification: ULT3580-TD5
 Product revision level: 252D
 Unit serial number: 70000033
 NAA: 30:11:22:33:ab:1:00:3
 Compression: factor 1 enabled 1


dump_tape:

PCL is : IBM003L5
Media density code: 0x58
Media type code   : 0x0b
Media description : Ultrium 5/16T
Tape Capacity     : 524288000
Remaining Tape Capacity : 0
Total num of filemarks: 3
Hdr:   Compressed data(0b), sz     20/80    , Blk No.: 0, data 0
Hdr:   Compressed data(0b), sz     56/80    , Blk No.: 1, data 20
Hdr:   Compressed data(0b), sz     27/80    , Blk No.: 2, data 76
Hdr:   Compressed data(0b), sz     24/80    , Blk No.: 3, data 103
Hdr:         Filemark(03), sz             0, Blk No.: 4, data 127
Hdr:   Compressed data(0b), sz  44226/262144, Blk No.: 5, data 127
Hdr:   Compressed data(0b), sz  35084/262144, Blk No.: 6, data 44353
Hdr:   Compressed data(0b), sz  45887/262144, Blk No.: 7, data 79437
Hdr:   Compressed data(0b), sz  41954/262144, Blk No.: 8, data 125324
.
.
.
.
Hdr:   Compressed data(0b), sz 256312/262144, Blk No.: 4573, data 521260664
Hdr:         Filemark(03), sz             0, Blk No.: 4574, data 521516976
Hdr:   Compressed data(0b), sz     61/80    , Blk No.: 4575, data 521516976
Hdr:   Compressed data(0b), sz     27/80    , Blk No.: 4576, data 521517037
Hdr:   Compressed data(0b), sz     24/80    , Blk No.: 4577, data 521517064
Hdr:         Filemark(03), sz             0, Blk No.: 4578, data 521517088
Hdr:      End of Data(05), sz             0, Blk No.: 4579, data 521517088

I will test more once Mark confirms any additional fixes for this patch.

-nia
Reply | Threaded
Open this post in threaded view
|  
Report Content as Inappropriate
star

Re: RFC: REPORT DENSITY rework.. (TSM LTO4 - LTO5 support ?)

Mark Harvey
any chance of sending me the syslog for the backup/restore tests ?

Just want to see what TSM actually uses ;)

Cheers
nia
Reply | Threaded
Open this post in threaded view
|  
Report Content as Inappropriate
star

Re: RFC: REPORT DENSITY rework.. (TSM LTO4 - LTO5 support ?)

nia
Administrator
Please find it attached here.

messages
Reply | Threaded
Open this post in threaded view
|  
Report Content as Inappropriate
star

Re: RFC: REPORT DENSITY rework.. (TSM LTO4 - LTO5 support ?)

Mark Harvey
Many thanks for testing and the messages file.

Looks like I'm on the right track.

I'll paste an update within the next few days.

Cheers
Mark
Loading...