Summary: Bad SDLT 320 - updates?

From: Sumeet Chandwani (sumeetpchandwani_at_yahoo.com)
Date: 02/09/05

  • Next message: Luis Manuel Sanchez Garcia: "V440 + ALOM + KVM" 
    Date: Wed, 9 Feb 2005 04:00:23 -0800 (PST)
To: sunmanagers@sunmanagers.org

    Hi,

    The E450 server had a A1000 storage connected to it
    along with DLT 7000 drive. The controller id's on DLT
    & A1000 storage was same (5). Changed the controller
    id on DLT drive & tested backup.

    While taking ufsdump got some file system inode
    related errors & ufsdump asked if u want to restart
    the backup. Replied No. ufsdump skipped the current
    f/s with errors & continued to next file system.
    Backup completed successfully & wrking fine now for
    3-4 days.

    Cheers,
    Sumeet.

    --- Sumeet Chandwani <sumeetpchandwani@yahoo.com>
    wrote:

    > Hi ,
    >
    > I was facing similar problems as mentioned in the
    > mail
    > below from Chris. Current Setup is E450 server with
    > DLT 7000 drive connected to it.
    >
    > Feb 4 16:46:56 vmail scsi: [ID 107833 kern.warning]
    > WARNING: /pci@1f,4000/scsi@2/st@4,0 (st11):
    > Feb 4 16:46:56 SCSI transport failed: reason
    > 'incomplete': retrying command
    > Feb 4 16:46:57 scsi: [ID 107833 kern.warning]
    > WARNING: /pci@1f,4000/scsi@2/st@4,0 (st11):
    > Feb 4 16:46:57 SCSI transport failed: reason
    > 'incomplete': giving up
    >
    >
    > DUMP: Writing 32 Kilobyte records
    > DUMP: Date of this level 0 dump: Fri Feb 04
    > 15:41:47
    > 2005
    > DUMP: Date of last level 0 dump: the epoch
    > DUMP: Dumping /dev/rdsk/c0t0d0s0 (/) to
    > /dev/rmt/1cn.
    > DUMP: Mapping (Pass I) [regular files]
    > DUMP: Mapping (Pass II) [directories]
    > DUMP: Estimated 7316156 blocks (3572.34MB).
    > DUMP: Dumping (Pass III) [directories]
    > DUMP: Dumping (Pass IV) [regular files]
    > DUMP: 48.59% done, finished in 0:10
    > DUMP: Write error 31340 feet into tape 1
    > DUMP: NEEDS ATTENTION: Do you want to restart?:
    > ("yes" or "no")
    > DUMP: NEEDS ATTENTION: Do you want to restart?:
    > ("yes" or "no")
    > DUMP: NEEDS ATTENTION: Do you want to restart?:
    > ("yes" or "no")
    > DUMP: NEEDS ATTENTION: Do you want to restart?:
    > ("yes" or "no")
    > DUMP: NEEDS ATTENTION: Do you want to restart?:
    > ("yes" or "no")
    > DUMP: NEEDS ATTENTION: Do you want to restart?:
    > ("yes" or "no")
    > DUMP: NEEDS ATTENTION: Do you want to restart?:
    > ("yes" or "no") no
    > DUMP: The ENTIRE dump is aborted.
    > DUMP: Writing 32 Kilobyte records
    > DUMP: Date of this level 0 dump: Fri Feb 04
    > 16:47:47
    > 2005
    > DUMP: Date of last level 0 dump: the epoch
    > DUMP: Dumping /dev/rdsk/c10t5d0s0 (/sunone) to
    > /dev/rmt/1cn.
    > DUMP: Mapping (Pass I) [regular files]
    > DUMP: Mapping (Pass II) [directories]
    > DUMP: Estimated 55534568 blocks (27116.49MB).
    > DUMP: NEEDS ATTENTION: Cannot open
    > `vmail:/dev/rmt/1cn'. Do you want to retry the
    > open?:
    > ("yes" or "no") YES
    > DUMP: NEEDS ATTENTION: Cannot open
    > `vmail:/dev/rmt/1cn'. Do you want to retry the
    > open?:
    > ("yes" or "no") yes
    > DUMP: NEEDS ATTENTION: Cannot open
    > `vmail:/dev/rmt/1cn'. Do you want to retry the
    > open?:
    > ("yes" or "no")
    >
    > After that DLT does not detected (mt command fails)
    > &
    > I hv to restart the DLT.
    >
    > Could you provide any insights / suggestions abt the
    > same.
    > Any help would be highly appreciated.
    >
    > Thanks & Regards,
    > Sumeet
    >
    >
    >
    >
    > Mail from Chris:-
    > Bad SDLT 320?
    >
    > Before I go to all the trouble of trying to get Sun
    > to
    > replace my tape
    > drive, I wanted to tap some of the experience that's
    > on this list to
    > see if what I'm seeing would point to a bad tape
    > drive.
    >
    > Have a V240 hooked up to a Sun SDLT 320 drive. Up
    > until this week it was
    > backing up ~60 Gigs worth of data using AMANDA (been
    > doing so for 7
    > months). That 60 gigs is spread across 3 servers, 1
    > of
    > which 1 is local
    > and the rest are remote.
    >
    > When AMANDA does backups, it'll consistently fail on
    > a
    > remote 25 gig
    > partition (and only this partition). The errors that
    > AMANDA gives
    > (which from my understanding are just passed along
    > dump errors) are:
    >
    > devl2 /dev/md/dsk/d8 lev 0 FAILED [out of
    > tape]
    > devl2 /dev/md/dsk/d8 lev 0 FAILED ["data
    > write:
    > Broken pipe"]
    > devl2 /dev/md/dsk/d8 lev 0 FAILED [dump to
    > tape
    > failed]
    >
    > After this the tape drive is unresponsive to any
    > commands, and the
    > following errors show up in /var/adm/messages:
    >
    > Aug 26 09:10:54 prod2 scsi: [ID 107833 kern.warning]
    > WARNING: /pci@1c,600000/scsi@2,1/st@5,0 (st12):
    > Aug 26 09:10:54 prod2 SCSI transport failed:
    > reason
    > 'incomplete':
    > retrying command
    > Aug 26 09:10:56 prod2 scsi: [ID 107833 kern.warning]
    > WARNING: /pci@1c,600000/scsi@2,1/st@5,0 (st12):
    > Aug 26 09:10:56 prod2 SCSI transport failed:
    > reason
    > 'incomplete':
    > retrying command
    > Aug 26 09:10:57 prod2 scsi: [ID 107833 kern.warning]
    > WARNING: /pci@1c,600000/scsi@2,1/st@5,0 (st12):
    > Aug 26 09:10:57 prod2 SCSI transport failed:
    > reason
    > 'incomplete':
    > giving up
    > Aug 26 09:26:39 prod2 scsi: [ID 365881
    > kern.info] /pci@1c,600000/scsi@2,1 (glm1):
    > Aug 26 09:26:39 prod2 Cmd (0x1b37578) dump for
    > Target 5 Lun 0:
    > Aug 26 09:26:39 prod2 scsi: [ID 365881
    > kern.info] /pci@1c,600000/scsi@2,1 (glm1):
    > Aug 26 09:26:39 prod2 cdb=[ 0xa 0x0 0x0
    > 0x80
    > 0x0 0x0 ]
    > Aug 26 09:26:39 prod2 scsi: [ID 365881
    > kern.info] /pci@1c,600000/scsi@2,1 (glm1):
    > Aug 26 09:26:39 prod2 pkt_flags=0x0
    > pkt_statistics=0x61 pkt_state=0x7
    > Aug 26 09:26:39 prod2 scsi: [ID 365881
    > kern.info] /pci@1c,600000/scsi@2,1 (glm1):
    > Aug 26 09:26:39 prod2 pkt_scbp=0x0
    > cmd_flags=0x18e1
    > Aug 26 09:26:39 prod2 scsi: [ID 107833 kern.warning]
    > WARNING: /pci@1c,600000/scsi@2,1 (glm1):
    > Aug 26 09:26:39 prod2 Disconnected command timeout
    > for Target 5.0
    > Aug 26 09:26:39 prod2 genunix: [ID 408822 kern.info]
    > NOTICE: glm1: fault
    > detected in device; service still available
    > Aug 26 09:26:39 prod2 genunix: [ID 611667 kern.info]
    > NOTICE: glm1:
    > Disconnected command timeout for Target 5.0
    > Aug 26 09:26:39 prod2 glm: [ID 160360 kern.warning]
    > WARNING:
    > ID[SUNWpd.glm.cmd_timeout.6016]
    > Aug 26 09:26:39 prod2 scsi: [ID 107833 kern.warning]
    > WARNING: /pci@1c,600000/scsi@2,1/st@5,0 (st12):
    > Aug 26 09:26:39 prod2 SCSI transport failed:
    > reason
    > 'timeout': giving
    > up
    >
    >
    > Cycling the tape drive will have it respond to mt
    > again.
    >
    > If I try to do a dump manually from the local
    > machine,
    > I'll consistently
    > get:
    >
    > </> # ufsdump -0f /dev/rmt/1n /dev/md/dsk/d6
    > DUMP: Writing 32 Kilobyte records
    > DUMP: Date of this level 0 dump: Thu Aug 26
    > 09:05:39
    > 2004
    > DUMP: Date of last level 0 dump: the epoch
    > DUMP: Dumping /dev/md/rdsk/d6 (prod2:/prod) to
    > /dev/rmt/1n.
    > DUMP: Mapping (Pass I) [regular files]
    > DUMP: Mapping (Pass II) [directories]
    > DUMP: Estimated 35790376 blocks (17475.77MB).
    > DUMP: Dumping (Pass III) [directories]
    > DUMP: Dumping (Pass IV) [regular files]
    >
    === message truncated ===
    Tired of spam? Yahoo! Mail has the best spam protection around
    http://mail.yahoo.com
    _______________________________________________
    sunmanagers mailing list
    sunmanagers@sunmanagers.org
    http://www.sunmanagers.org/mailman/listinfo/sunmanagers

  • Next message: Luis Manuel Sanchez Garcia: "V440 + ALOM + KVM"

    Relevant Pages

    • Solaris 8 ufsdump limitations?
      ... Are there any limits on solaris 8 ufsdump? ... I have a DLT VS160 tape drive connected to a Blade 1000 machine ... DUMP: Estimated 65067820 blocks. ...
      (comp.unix.solaris)
    • SUMMARY: old tape backups..(a bit late..)
      ... I will try to find a company which transfers data from old tape to ... can find a working DLT 2000, ... specializes in transferring data on older media to ... They're likely to have working drives. ...
      (Tru64-UNIX-Managers)
    • Re: DLT 4000 dying from heat?
      ... to eject the tape, and also load the tape, but the SCSI-interface ... If I wait for 15 minutes, then the DLT boots correctly (LEDs are off) ... It might give you a better error message, ...
      (comp.arch.storage)
    • Re: NT Backup Not Recognize Tape from another server.
      ... Greg is correct.."should an NTBackup of SBS onto a DLT tape be readable by ... The tapes are Exactly the same tape, ... When blank the tapes can be read/write by either server or drive. ... are your DLT tape drives the same capacity? ...
      (microsoft.public.windows.server.sbs)
    • Re: NT Backup Not Recognize Tape from another server.
      ... different SBS server that has a DLT drive?" ... The tapes are Exactly the same tape, ... When blank the tapes can be read/write by either server or drive. ...
      (microsoft.public.windows.server.sbs)