HPE GreenLake Administration
- Community Home
- >
- Servers and Operating Systems
- >
- Operating Systems
- >
- Operating System - HP-UX
- >
- DUMP aborts ....??
Operating System - HP-UX
1834462
Members
3236
Online
110067
Solutions
Forums
Categories
Company
Local Language
back
Forums
Discussions
Forums
- Data Protection and Retention
- Entry Storage Systems
- Legacy
- Midrange and Enterprise Storage
- Storage Networking
- HPE Nimble Storage
Discussions
Forums
Discussions
Discussions
Discussions
Forums
Discussions
back
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
- BladeSystem Infrastructure and Application Solutions
- Appliance Servers
- Alpha Servers
- BackOffice Products
- Internet Products
- HPE 9000 and HPE e3000 Servers
- Networking
- Netservers
- Secure OS Software for Linux
- Server Management (Insight Manager 7)
- Windows Server 2003
- Operating System - Tru64 Unix
- ProLiant Deployment and Provisioning
- Linux-Based Community / Regional
- Microsoft System Center Integration
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Blogs
Information
Community
Resources
Community Language
Language
Forums
Blogs
Go to solution
Topic Options
- Subscribe to RSS Feed
- Mark Topic as New
- Mark Topic as Read
- Float this Topic for Current User
- Bookmark
- Subscribe
- Printer Friendly Page
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
06-19-2001 12:32 AM
06-19-2001 12:32 AM
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.
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.
Solved! Go to Solution.
3 REPLIES 3
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
06-19-2001 12:54 AM
06-19-2001 12:54 AM
Re: DUMP aborts ....??
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.
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.
Marcin Wicinski
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
06-19-2001 12:56 AM
06-19-2001 12:56 AM
Re: DUMP aborts ....??
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
You might also want to check whether the tape length is set correctly in your command.
Carsten
-------------------------------------------------------------------------------------------------
In the beginning the Universe was created. This has made a lot of people very angry and been widely regarded as a bad move. -- HhGttG
In the beginning the Universe was created. This has made a lot of people very angry and been widely regarded as a bad move. -- HhGttG
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
06-19-2001 01:17 AM
06-19-2001 01:17 AM
Solution
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
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
Regards,
John
The opinions expressed above are the personal opinions of the authors, not of Hewlett Packard Enterprise. By using this site, you accept the Terms of Use and Rules of Participation.
Company
Events and news
Customer resources
© Copyright 2025 Hewlett Packard Enterprise Development LP