Storage Boards Cleanup
To make it easier to find information about HPE Storage products and solutions, we are doing spring cleaning. This includes consolidation of some older boards, and a simpler structure that more accurately reflects how people use HPE Storage.
Tape Libraries and Drives
cancel
Showing results for 
Search instead for 
Did you mean: 

fbackup with failure

Mann_2
Frequent Advisor

fbackup with failure

Hello experts,

i have search in the newsgroups my failure, but without a hit!

I do not understand well English and it can be therefore which I mean solution already surveyed.

I have a problem with an LTO HP Ultrium 230i.

The Device hang on a HPUX 10.20 Server, in a external Storage on the SE-Bus.

The device was exchange yesterday while the device before was defective.

The Attitudes was exactly as the device before(SCSI-ID)

A Textfile of the ioscan was in the Attachment.

I use fbackup for the backup and recovery, and before the exchange he was functionally.

But after the exchange, i cant't use fbackup:

fbackup(1004): session begins on Sat Apr 12 21:08:49 2003
fbackup(3038): output file /dev/rmt/1m is not a valid device file for backup
fbackup(3019): would you like to enter a new output file?

What's the problem?

an ioscan -fnkCtape:

ioscan -fnkCtape
Class I H/W Path Driver S/W State H/W Type Description
=====================================================================
tape 0 8/16/5.0.0 stape CLAIMED DEVICE HP C1537A
/dev/rmt/0m /dev/rmt/0mnb /dev/rmt/c1t0d0DDSb
/dev/rmt/0mb /dev/rmt/c1t0d0BEST /dev/rmt/c1t0d0BESTnb /dev/rmt/c1t0d0DDSn /dev/rmt/0mn dev/rmt/c1t0d0BESTb /dev/rmt/c1t0d0DDS
/dev/rmt/c1t0d0DDSnb
tape 1 8/16/5.1.0 stape CLAIMED DEVICE HP Ultrium 1-SCSI
/dev/rmt/1m /dev/rmt/1mn /dev/rmt/c1t1d0BEST /dev/rmt/c1t1d0BESTn /dev/rmt/1mb /dev/rmt/1mnb/dev/rmt/c1t1d0BESTb /dev/rmt/c1t1d0BESTnb
-----------------------------------------------The ioscan lists the device-file.

Why i can't use these or one of the files(rmt/1m or c1t1d0BEST).

I try isnf -e to recreate new files, without success!

Before this misfire i could use fbackup with little files (example the /tmp - directory),

But as i try fbackup with great files, i became the failure:

fbackup(3024): writing volume 1 to the output file /dev/rmt/c1t1d0BEST
fbackup(3012): WRITE ERROR while writing checkpoint record, at media record 118528
fbackup(3102): attempting to make this volume salvagable
fbackup(3123): could not read the previous checkpoint record
fbackup(3105): writing 2 EOFs and rewinding the tape

-----------------------------------------------
I modified the file:

#fbackup_config
blocksperrecord 64
records 64
checkpointfreq 256
readerprocesses 2
maxretries 7
retrylimit 5000000
maxvoluses 200
filesperfsm 200

So i can use the Ultrium on the SE-BUS(approximately the shoe-shinning effect, buffer-underrun)!

has the new device again a failure?

thanks for help an kind regards

roland

Roland
2 REPLIES
Michael Steele_2
Honored Contributor

Re: fbackup with failure

These patches are indicated: PHSS_26881 and PHSS_27585

You may have a bad SCSI cable and not a bad device.

What does LOGTOOL say about this HW path: 8/16/5.1.0?

STM > TOOLS > UTILITY > RUN > LOGTOOL > FILE > VIEW > RAW SUMMARY.

Note the first and last dates of transactions and calculate the difference. If the difference is short, like 4 hours, then this is important to note. Now read down the report of hardware addresses and observe the integer numbers in parenthesis. Anything over 150 in this 4 hour period should be called into HP for replacement.

Also check /etc/rc.log, syslog.log and /var/adm/messages (* dmesg *).
Support Fatherhood - Stop Family Law
Mann_2
Frequent Advisor

Re: fbackup with failure

Michael,

thanks for the answer. I look
in the logfiles and yes, you have right:

in the RAW-File-Log i see that the stape on the Hw-Path 8/16/5.... makes over 240 errors.

The failure came really from cable!

great thanks for your help!!

best regards

roland
Roland