topic Re: DUMP aborts ....?? in Operating System - HP-UX

DUMP aborts ....??

Lucien Wolfs — Tue, 19 Jun 2001 07:32:43 GMT

For some undocumented reason, dump aborts with a message I cannot explain. Perhaps somebody can help me. DUMP ends with errorcode 3. (Nothing in the man-pages about the explenation of errorcodes)

Here's the log

DUMP: Date of this level 0 dump: Tue Jun 19 00:19:27 2001
DUMP: Date of last level 0 dump: the epoch
DUMP: Dumping /dev/vg00/rlvol1 (/) to /dev/rmt/c12t6d0BESTn
DUMP: This is an HP long file name filesystem
DUMP: mapping (Pass I) [regular files]
DUMP: mapping (Pass II) [directories]
DUMP: estimated 63042 tape blocks on 1.62 tape(s).
DUMP: dumping (Pass III) [directories]
DUMP: dumping (Pass IV) [regular files]
DUMP: Change Tapes: Mount tape #2
DUMP: fopen on /dev/tty fails
DUMP: The ENTIRE dump is aborted.

Re: DUMP aborts ....??

Marcin Wicinski — Tue, 19 Jun 2001 07:54:07 GMT

Hi,

The log message:

DUMP: fopen on /dev/tty fails
DUMP: The ENTIRE dump is aborted,

indicates known problem, when specified device (here it is /dev/rmt/c12t6d0BESTn) is not accessible.

Check if /dev/rmt/c12t6d0BESTn is present and works fine.

Re: DUMP aborts ....??

Carsten Krege — Tue, 19 Jun 2001 07:56:39 GMT

Try to specify the tape device in your command line by putting the hostname in front of it ":/dev/rmt/c12t6d0BESTn".

You might also want to check whether the tape length is set correctly in your command.

Carsten

Re: DUMP aborts ....??

John Palmer — Tue, 19 Jun 2001 08:17:05 GMT

dump is an old utility that defaults to assuming that it is writing to tape devices that have very limited capacity.

In your case, it has calculated that the 63042 tape blocks will require 1.62 tape volumes. Thus when it thinks that it is approaching end of tape, it closes the tape and asks you to load the second one.

Dump also expects to have a controlling terminal that it can interact with to request a new tape. In your case dump is running as a background job (from cron or something) so having failed to open the controlling terminal (/dev/tty) it simply fails.

The solution is to change the arguments to dump so that it will never attempt to close a tape volume other than when it encounters the physical end of a tape. Try specifying the following arguments:-

dump 0bdfs 64 62000 999999

Regards,
John