topic Errors in fbackup log in Operating System - HP-UX

Errors in fbackup log

Markus Hoeschen — Tue, 13 Nov 2001 08:51:09 GMT

Hi all,

I??m using fbackup. Since yesterday there are some errors in my fbackup log file. I can??t find any infos about them on the HP-Website. Can anybody help me?

Here is the (error) part of my logfile:

fbackup(9999): Interrupted system call
fbackup(9999): Interrupted system call
fbackup(2004): reader 1: 1st read error, firstread=32768, n=0
fbackup(2004): reader 0: 1st read error, firstread=32768, n=0
fbackup(9999): Interrupted system call
fbackup(2004): reader 0: 1st read error, fbackup(9999): Interrupted system call
fbackup(2004): reader 1: 1st read error, firstread=32768, n=0
fbackup(9999): Interrupted system call
fbackup(2004): reader 1: 1st read error, firstread=32768, n=0
firstread=163840, n=0
fbackup(9999): Interrupted system call
fbackup(2004): reader 1: 1st read error, firstread=32768, n=0
fbackup(9999): Interrupted system call
fbackup(2004): reader 1: 1st read error, firstread=32768, n=0
fbackup(9999): Interrupted system call
fbackup(2004): reader 1: 1st read error, firstread=32768, n=0
fbackup(9999): Interrupted system call
fbackup(2004): reader 1: 1st read error, firstread=32768, n=0
fbackup(9999): Interrupted system call
fbackup(2004): reader 1: 1st read error, firstread=32768, n=0
fbackup(9999): Interrupted system call
fbackup(2004): reader 1: 1st read error, firstread=32768, n=0
fbackup(9999): Interrupted system call
fbackup(2004): reader 1: 1st read error, firstread=32768, n=0
fbackup(9999): Interrupted system call
fbackup(2004): reader 1: 1st read error, firstread=32768, n=0
fbackup(9999): Interrupted system call
fbackup(2004): reader 1: 1st read error, firstread=25908, n=0

Re: Errors in fbackup log

Frank Slootweg — Tue, 13 Nov 2001 12:50:51 GMT

If I remember correctly, you get this error when there are (read) I/O errors when reading the file(s).

If you have not already done so, then add the "-v" option to the fbackup command. That will probably report *which* files are having problems. If so, you can try to cp(1) or cat(1) these files to /dev/null. That will probably also give errors. If so, you know you have a disk problem.

If you do not know which files, but do know which filesystem, or need to know which disks are involved, then do a bdf(1M) to get the LV name for the filesystem, a "lvdisplay -v /dev/vg??/lvol?" to get the /dev/dsk/... names of the PVs/disks, a lssf(1M) to get the hardware addresses, a "ioscan -f -H ..." to get the "Description" of the disks.

Re: Errors in fbackup log

Sanjay_6 — Tue, 13 Nov 2001 14:56:42 GMT

Hi,

Try some fbackup patches. Look for the fbackup patch for your version of ux,

From ITRC Home --> Individual patches --> HP-ux patches --> select keyword as fbackup and select your version of ux.

Have a look at the threads below,

http://us-support.external.hp.com/cki/bin/doc.pl/sid=82d32ab60ea75fd540/screen=ckiDisplayDocument?docId=200000006395590

http://us-support.external.hp.com/cki/bin/doc.pl/sid=82d32ab60ea75fd540/screen=ckiDisplayDocument?docId=400000000227984

hope this helps.

Regds