ADSM-L

Re: [ADSM-L] write failed using tsm but write successful vi tar command

2007-12-24 04:49:15
Subject: Re: [ADSM-L] write failed using tsm but write successful vi tar command
From: CAYE PIERRE <Pierre.Caye AT ALCATEL-LUCENT DOT FR>
To: ADSM-L AT VM.MARIST DOT EDU
Date: Mon, 24 Dec 2007 10:48:35 +0100
It can be a cartridge problems too

Had you changed the output cartridge ?

If tapeutil failed, check errlog then call AIX support 

> -----Message d'origine-----
> De : ADSM: Dist Stor Manager [mailto:ADSM-L AT VM.MARIST DOT EDU] De 
> la part de hshahizul
> Envoyé : vendredi 21 décembre 2007 18:18
> À : ADSM-L AT VM.MARIST DOT EDU
> Objet : Re: [ADSM-L] write failed using tsm but write 
> successful vi tar command
> 
> Thanks Mr. Caye Pierre.
> 
> I will try this again. I have done it as well. I'm suspecting 
> error come from SCSI cable or terminator. (wild guest while 
> looking at error report).
> I will post the result next week since I will be on leave for 
> a week. My local time (Malaysia) is midnight.
> 
> Mercy.
> 
> Zul. 
> 
> -----Original Message-----
> From: ADSM: Dist Stor Manager [mailto:ADSM-L AT VM.MARIST DOT EDU] 
> On Behalf Of CAYE PIERRE
> Sent: Friday, December 21, 2007 11:39 PM
> To: ADSM-L AT VM.MARIST DOT EDU
> Subject: Re: [ADSM-L] write failed using tsm but write 
> successful vi tar command
> 
> Errno 5 mean I/O Error for AIX
> 
> So try :
> 
>  rmdev -l rmt0
>  mkdev -l rmt0
> 
> Then retry a migration 
> 
> > -----Message d'origine-----
> > De : ADSM: Dist Stor Manager [mailto:ADSM-L AT VM.MARIST DOT EDU] 
> De la part 
> > de hshahizul Envoyé : vendredi 21 décembre 2007 16:36 À : 
> > ADSM-L AT VM.MARIST DOT EDU Objet : Re: [ADSM-L] write failed 
> using tsm but 
> > write successful vi tar command
> > 
> > I managed to label the tape. I managed to checkin the volume. 
> > While the migration processes start, the volume is mounted in the 
> > drive. I can see from console that the volume is mounted in 
> the drive. 
> > The problem is while writing.
> > 
> > Anyway, thanks for your idea.
> > 
> > -----Original Message-----
> > From: ADSM: Dist Stor Manager [mailto:ADSM-L AT VM.MARIST DOT EDU] 
> On Behalf 
> > Of CAYE PIERRE
> > Sent: Friday, December 21, 2007 11:32 PM
> > To: ADSM-L AT VM.MARIST DOT EDU
> > Subject: Re: [ADSM-L] write failed using tsm but write 
> successful vi 
> > tar command
> > 
> > Had you labeled the tapes ?
> > 
> >  
> > 
> > > -----Message d'origine-----
> > > De : ADSM: Dist Stor Manager [mailto:ADSM-L AT VM.MARIST DOT EDU]
> > De la part
> > > de hshahizul Envoyé : vendredi 21 décembre 2007 16:26 À : 
> > > ADSM-L AT VM.MARIST DOT EDU Objet : Re: [ADSM-L] write failed
> > using tsm but
> > > write successful vi tar command
> > > 
> > > No, but I will try to do that. Anyway, no harm trying.
> > > Thanks for the idea
> > > 
> > > -----Original Message-----
> > > From: ADSM: Dist Stor Manager [mailto:ADSM-L AT VM.MARIST DOT EDU]
> > On Behalf
> > > Of Helder Garcia
> > > Sent: Friday, December 21, 2007 3:31 AM
> > > To: ADSM-L AT VM.MARIST DOT EDU
> > > Subject: Re: [ADSM-L] write failed using tsm but write
> > successful vi
> > > tar command
> > > 
> > > hi, did you tried using mt0 instead of rmt0?
> > > 
> > > On Dec 17, 2007 1:27 PM, hshahizul <hshahizul AT gmail DOT com> wrote:
> > > 
> > > > Some one pleases help. I'm stuck more then a week for 
> this error.
> > > >
> > > >
> > > >
> > > > TSM Server 5.4.0.0
> > > >
> > > > AIX 5.3
> > > >
> > > > Tape Library TS3100 (single drive)
> > > >
> > > > Atape Driver 9.7.5.0
> > > >
> > > >
> > > >
> > > > dev type : LTO
> > > >
> > > > devc format : ultrium3c
> > > >
> > > > Drive Ultrium3
> > > >
> > > >
> > > >
> > > > # lsdev -Cc tape
> > > >
> > > > rmt0 Available 07-08-00-4,0 IBM 3580 Ultrium Tape Drive
> > > >
> > > > smc0 Available 07-08-00-4,1 IBM 3573 Tape Medium Changer
> > > >
> > > >
> > > >
> > > >
> > > >
> > > > # lscfg -vl rmt0
> > > >
> > > >  rmt0             U787B.001.DNWG37G-P1-C5-T1-L4-L0  IBM 
> > > 3580 Ultrium Tape
> > > > Drive
> > > >
> > > >
> > > >
> > > >        Manufacturer................IBM
> > > >
> > > >        Machine Type and Model......ULT3580-TD3
> > > >
> > > >        Serial Number...............1210283884
> > > >
> > > >        Device Specific.(FW)........73P5
> > > >
> > > >
> > > >
> > > > # lscfg -vl smc0
> > > >
> > > >  smc0  U787B.001.DNWG37G-P1-C5-T1-L4-L1  IBM 3573 Tape
> > > Medium Changer
> > > >
> > > >
> > > >
> > > >        Manufacturer................IBM
> > > >
> > > >        Machine Type and Model......3573-TL
> > > >
> > > >        Serial Number...............00L2U78C2421_LL0
> > > >
> > > >        Device Specific.(FW)........3.70
> > > >
> > > >
> > > >
> > > >
> > > >
> > > >
> > > >
> > > > I have tried to migrate from diskpool to tapepool but 
> failed with 
> > > > error
> > > >
> > > > ANR8311E An I/O error occurred while accessing drive
> > > >
> > > > DRIVE1 (/dev/rmt0) for WRITE operation, errno = 5.
> > > >
> > > >
> > > >
> > > > I tried to write via tar command [ tar -cvf /dev/rmt0 
> /tmp ]. It 
> > > > successfull write to tape
> > > >
> > > >
> > > >
> > > > I tried to used tapeutil facility (halt TSM Server)
> > > >
> > > >
> > > >
> > > >
> > > >
> > > > Without lto3 tape inside tape drive : option 37 (write)
> > > >
> > > > .....
> > > >
> > > > Writing file to tape...
> > > >
> > > > Write terminated, 0 total bytes written...
> > > >
> > > > Operation failed with errno 46: Device not ready
> > > >
> > > > Residual count: 4125543
> > > >
> > > > Error Sense Data,  Length 96
> > > >
> > > >
> > > >
> > > > With lto3 tape mount inside tape drive : option 37 (write)
> > > >
> > > > ......
> > > >
> > > > Writing file to tape...
> > > >
> > > > Write terminated, 0 total bytes written...
> > > >
> > > > Operation failed with errno 5: I/O error
> > > >
> > > > Residual count: 4125543
> > > >
> > > >
> > > >
> > > >
> > > >
> > > > I have tried to install TSM 5.5 and Atape 10.3.7.0 but the
> > > result  is
> > > > still the same.
> > > >
> > > > I also tried to update devclass class=drive , but still the
> > > same output.
> > > >
> > > >
> > > >
> > > > The question here, why via tar command , tape can be 
> written but 
> > > > cannot via TSM
> > > >
> > > >
> > > >
> > > > Tq.
> > > >
> > > >
> > > >
> > > >
> > > >
> > > >
> > > >
> > > > Additional Info
> > > >
> > > > One more things, while the process of migration take place
> > > AIX error
> > > > report produce as below:
> > > >
> > > >
> > > >
> > > > ========================================
> > > >
> > > > LABEL:          TAPE_ERR4
> > > >
> > > > IDENTIFIER:     5537AC5F
> > > >
> > > >
> > > >
> > > > Date/Time:       Mon Dec 17 22:06:25 WAUST 2007
> > > >
> > > > Sequence Number: 2782
> > > >
> > > > Machine Id:      000535C7D600
> > > >
> > > > Node Id:         db3
> > > >
> > > > Class:           H
> > > >
> > > > Type:            PERM
> > > >
> > > > Resource Name:   rmt0
> > > >
> > > > Resource Class:  tape
> > > >
> > > > Resource Type:   3580
> > > >
> > > > Location:        U787B.001.DNWG37G-P1-C5-T1-L4-L0
> > > >
> > > > VPD:
> > > >
> > > >        Manufacturer................IBM
> > > >
> > > >        Machine Type and Model......ULT3580-TD3
> > > >
> > > >        Serial Number...............1210283884
> > > >
> > > >        Device Specific.(FW)........73P5
> > > >
> > > >
> > > >
> > > > Description
> > > >
> > > > TAPE DRIVE FAILURE
> > > >
> > > >
> > > >
> > > > Probable Causes
> > > >
> > > > ADAPTER
> > > >
> > > > TAPE DRIVE
> > > >
> > > >
> > > >
> > > > Failure Causes
> > > >
> > > > ADAPTER
> > > >
> > > > TAPE DRIVE
> > > >
> > > >
> > > >
> > > >            Recommended Actions
> > > >
> > > >            PERFORM PROBLEM DETERMINATION PROCEDURES
> > > >
> > > >
> > > >
> > > > Detail Data
> > > >
> > > > SENSE DATA
> > > >
> > > > 0604 0000 0A00 0400 0000 0000 0000 0000 0200 0200 0000 0000
> > > 0000 0000
> > > > 0000 0000
> > > >
> > > > 0000 0000 0000 0000 0000 0000 0000 0000 0000 0000 0000 0000
> > > 0000 0000
> > > > 0000 0000
> > > >
> > > > 0000 0000 0000 0000 0000 0000 0000 0000 0000 0000 0000 0000
> > > 0000 0000
> > > > 0000 0000
> > > >
> > > > 0000 0000 0000 0000 0000 0000 0000 0000 0000 0000 0000 0000
> > > 0000 0000
> > > > 0000 0000
> > > >
> > > > 0000 0000 0000 0000 0000 0000 0000 0000 0000 0000 0000 0000
> > > 0000 0000
> > > >
> > > >
> > > >
> > > --------------------------------------------------------------
> > > -------------
> > > >
> > > > LABEL:          SCSI_ERR10
> > > >
> > > > IDENTIFIER:     0BA49C99
> > > >
> > > >
> > > >
> > > > Date/Time:       Mon Dec 17 22:06:25 WAUST 2007
> > > >
> > > > Sequence Number: 2781
> > > >
> > > > Machine Id:      000535C7D600
> > > >
> > > > Node Id:         db3
> > > >
> > > > Class:           H
> > > >
> > > > Type:            TEMP
> > > >
> > > > Resource Name:   scsi2
> > > >
> > > > Resource Class:  driver
> > > >
> > > > Resource Type:   sisscsi
> > > >
> > > > Location:        U787B.001.DNWG37G-P1-C5-T1
> > > >
> > > > VPD:
> > > >
> > > >        ROM Level.(alterable).......05080092
> > > >
> > > >        Product Specific.(CC).......5702
> > > >
> > > >
> > > >
> > > > Description
> > > >
> > > > SCSI BUS ERROR
> > > >
> > > >
> > > >
> > > > Probable Causes
> > > >
> > > > CABLE
> > > >
> > > > CABLE TERMINATOR
> > > >
> > > > DEVICE
> > > >
> > > > ADAPTER
> > > >
> > > >
> > > >
> > > > Failure Causes
> > > >
> > > > CABLE LOOSE OR DEFECTIVE
> > > >
> > > > DEVICE
> > > >
> > > > ADAPTER
> > > >
> > > >
> > > >
> > > >            Recommended Actions
> > > >
> > > >            PERFORM PROBLEM DETERMINATION PROCEDURES
> > > >
> > > >            CHECK CABLE AND ITS CONNECTIONS
> > > >
> > > >
> > > >
> > > > Detail Data
> > > >
> > > > SENSE DATA
> > > >
> > > > 0000 FFFF 1900 00F0 0629 0000 0301 0000 0508 0092 0000 00FF
> > > 5702 0000
> > > > 0000 0000
> > > >
> > > > E210 0080 FF00 0000 0310 0010 0D5A 89F9 0000 0000 0000 03E8
> > > 0629 0000
> > > > 0000 FFFF
> > > >
> > > > FFFF FFFF 1025 3380 0000 0000 28E2 0300 0000 0003 8300 0000
> > > 8000 0000
> > > > 8000 0000
> > > >
> > > > .....
> > > >
> > > >
> > > >
> > > >
> > > >
> > > --------------------------------------------------------------
> > > -------------
> > > >
> > > > LABEL:          TAPE_ERR4
> > > >
> > > > IDENTIFIER:     5537AC5F
> > > >
> > > >
> > > >
> > > > Date/Time:       Mon Dec 17 22:05:42 WAUST 2007
> > > >
> > > > Sequence Number: 2780
> > > >
> > > > Machine Id:      000535C7D600
> > > >
> > > > Node Id:         db3
> > > >
> > > > Class:           H
> > > >
> > > > Type:            PERM
> > > >
> > > > Resource Name:   rmt0
> > > >
> > > > Resource Class:  tape
> > > >
> > > > Resource Type:   3580
> > > >
> > > > Location:        U787B.001.DNWG37G-P1-C5-T1-L4-L0
> > > >
> > > > VPD:
> > > >
> > > >        Manufacturer................IBM
> > > >
> > > >        Machine Type and Model......ULT3580-TD3
> > > >
> > > >        Serial Number...............1210283884
> > > >
> > > >        Device Specific.(FW)........73P5
> > > >
> > > >
> > > >
> > > > Description
> > > >
> > > > TAPE DRIVE FAILURE
> > > >
> > > >
> > > >
> > > > Probable Causes
> > > >
> > > > ADAPTER
> > > >
> > > > TAPE DRIVE
> > > >
> > > >
> > > >
> > > > Failure Causes
> > > >
> > > > ADAPTER
> > > >
> > > > TAPE DRIVE
> > > >
> > > >
> > > >
> > > >            Recommended Actions
> > > >
> > > >            PERFORM PROBLEM DETERMINATION PROCEDURES
> > > >
> > > >
> > > >
> > > > Detail Data
> > > >
> > > > SENSE DATA
> > > >
> > > > 0604 0000 0A00 0400 0000 0000 0000 0000 0200 0200 0000 0000
> > > 0000 0000
> > > > 0000 0000
> > > >
> > > > 0000 0000 0000 0000 0000 0000 0000 0000 0000 0000 0000 0000
> > > 0000 0000
> > > > 0000 0000
> > > >
> > > > 0000 0000 0000 0000 0000 0000 0000 0000 0000 0000 0000 0000
> > > 0000 0000
> > > > 0000 0000
> > > >
> > > > 0000 0000 0000 0000 0000 0000 0000 0000 0000 0000 0000 0000
> > > 0000 0000
> > > > 0000 0000
> > > >
> > > > 0000 0000 0000 0000 0000 0000 0000 0000 0000 0000 0000 0000
> > > 0000 0000
> > > >
> > > >
> > > >
> > > --------------------------------------------------------------
> > > -------------
> > > >
> > > > LABEL:          SCSI_ERR10
> > > >
> > > > IDENTIFIER:     0BA49C99
> > > >
> > > >
> > > >
> > > > Date/Time:       Mon Dec 17 22:05:42 WAUST 2007
> > > >
> > > > Sequence Number: 2779
> > > >
> > > > Machine Id:      000535C7D600
> > > >
> > > > Node Id:         db3
> > > >
> > > > Class:           H
> > > >
> > > > Type:            TEMP
> > > >
> > > > Resource Name:   scsi2
> > > >
> > > > Resource Class:  driver
> > > >
> > > > Resource Type:   sisscsi
> > > >
> > > > Location:        U787B.001.DNWG37G-P1-C5-T1
> > > >
> > > > VPD:
> > > >
> > > >        ROM Level.(alterable).......05080092
> > > >
> > > >        Product Specific.(CC).......5702
> > > >
> > > >
> > > >
> > > > Description
> > > >
> > > > SCSI BUS ERROR
> > > >
> > > >
> > > >
> > > > Probable Causes
> > > >
> > > > CABLE
> > > >
> > > > CABLE TERMINATOR
> > > >
> > > > DEVICE
> > > >
> > > > ADAPTER
> > > >
> > > >
> > > >
> > > > Failure Causes
> > > >
> > > > CABLE LOOSE OR DEFECTIVE
> > > >
> > > > DEVICE
> > > >
> > > > ADAPTER
> > > >
> > > >
> > > >
> > > >            Recommended Actions
> > > >
> > > >            PERFORM PROBLEM DETERMINATION PROCEDURES
> > > >
> > > >            CHECK CABLE AND ITS CONNECTIONS
> > > >
> > > >
> > > >
> > > > Detail Data
> > > >
> > > > SENSE DATA
> > > >
> > > > 0000 FFFF 1900 00F0 0629 0000 0301 0000 0508 0092 0000 00FF
> > > 5702 0000
> > > > 0000 0000
> > > >
> > > > E210 0080 FF00 0000 0310 000F 0D18 D559 0000 0000 0000 03E8
> > > 0629 0000
> > > > 0000 FFFF
> > > >
> > > > ....
> > > >
> > > >
> > > >
> > > >
> > > >
> > > > Zul
> > > >
> > > 
> > > 
> > > 
> > > --
> > > Helder Garcia
> > > 
> > 
>