- Community Home
- >
- Servers and Operating Systems
- >
- Operating Systems
- >
- Operating System - HP-UX
- >
- make_net_recovery/pax: bogus file?
Operating System - HP-UX
1753641
Members
4907
Online
108798
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
Discussions
Discussions
Forums
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
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
тАО12-15-2003 01:38 AM
тАО12-15-2003 01:38 AM
make_net_recovery is failing with an error apparently out of pax. If I understand the log correctly, it's finding a bogus/corrupt file (looking for a file with windoze syntax?)
If this is the case, any suggestions on how to clean it out (find can't find it)?
If it's not the case, any ideas why make_net/pax is gacking?
* /opt/ignite/data/scripts/make_sys_image -d
/var/opt/ignite/recovery/arch_mnt -t n -s local -n 2003-12-11,12:39 -m
t -w /var/opt/ignite/recovery/client_mnt/0x00306E1BAC94/recovery/2003-
12-11,12:39/recovery.log -u -R -g /var/opt/ignite/recovery/client_mnt/
0x00306E1BAC94/recovery/2003-12-11,12:39/flist -a 6434000
* Preparing to create a system archive
* The archive is estimated to reach 3217000 kbytes.
* Free space on /var/opt/ignite/recovery/arch_mnt
after archive should be about 426072 kbytes.
* Archiving contents of torvalds via tar to
/var/opt/ignite/recovery/arch_mnt/2003-12-11,12:39.
pax: tmp/
ar\opt\OV\log\OpC\opcerror : No such file or directory
Press Q/q to quit, Enter to continue:
WARNING: The pax command returned a non-zero exit status (exit status 1)
* Creation of system archive complete
NOTE: The following files are in the list of files that were on the
system, but they are no longer present. These files are not
included in the back-up:
/var/tmp/ign_configure/make_sys_image.log
ERROR: The make_sys_image command failed. The system recovery archive will
not be created.
Thanks...
...Peter
If this is the case, any suggestions on how to clean it out (find can't find it)?
If it's not the case, any ideas why make_net/pax is gacking?
* /opt/ignite/data/scripts/make_sys_image -d
/var/opt/ignite/recovery/arch_mnt -t n -s local -n 2003-12-11,12:39 -m
t -w /var/opt/ignite/recovery/client_mnt/0x00306E1BAC94/recovery/2003-
12-11,12:39/recovery.log -u -R -g /var/opt/ignite/recovery/client_mnt/
0x00306E1BAC94/recovery/2003-12-11,12:39/flist -a 6434000
* Preparing to create a system archive
* The archive is estimated to reach 3217000 kbytes.
* Free space on /var/opt/ignite/recovery/arch_mnt
after archive should be about 426072 kbytes.
* Archiving contents of torvalds via tar to
/var/opt/ignite/recovery/arch_mnt/2003-12-11,12:39.
pax: tmp/
ar\opt\OV\log\OpC\opcerror : No such file or directory
Press Q/q to quit, Enter to continue:
WARNING: The pax command returned a non-zero exit status (exit status 1)
* Creation of system archive complete
NOTE: The following files are in the list of files that were on the
system, but they are no longer present. These files are not
included in the back-up:
/var/tmp/ign_configure/make_sys_image.log
ERROR: The make_sys_image command failed. The system recovery archive will
not be created.
Thanks...
...Peter
Solved! Go to Solution.
2 REPLIES 2
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
тАО12-15-2003 01:42 AM
тАО12-15-2003 01:42 AM
Re: make_net_recovery/pax: bogus file?
Never Mind!
Found the reference to flist in a previous post, used it to trace down the offender.
Found the reference to flist in a previous post, used it to trace down the offender.
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
тАО12-15-2003 02:13 AM
тАО12-15-2003 02:13 AM
Solution
Peter,
it's known problem that Ignite fails to backup files containing backslashes in their filenames. JAGaf01832.
Workaround:
Change the filter_dead_files() function, coded in the
script /opt/ignite/data/scripts/make_sys_image to use the -r option
with print:
filter_dead_files() {
# NREad from standard-in and then check for any files
# that are no longer on the system and remove them
# from the list. Also note that the files in the list
# have been stripped of their first "/". Therefore,
# it has been added for the test.
while read -r FILE_IN
do
# Check if file exists and is readable. If not, do not archive.
if [[ -r "/${FILE_IN}" || -L "/${FILE_IN}" || -S "/${FILE_IN}" \
|| -p "/${FILE_IN}" || -b "/${FILE_IN}" || -c "/${FILE_IN}" \
|| -d "/${FILE_IN}" || -f "/${FILE_IN}" ]]; then
# The calling program accepts all output, so just do so.
print -r -- "${FILE_IN}"
else
print -r " /${FILE_IN}" >> ${TMP_GONE_FILE_LIST}
fi
done
} # End filter_dead_files()
Best regards...
Dietmar.
it's known problem that Ignite fails to backup files containing backslashes in their filenames. JAGaf01832.
Workaround:
Change the filter_dead_files() function, coded in the
script /opt/ignite/data/scripts/make_sys_image to use the -r option
with print:
filter_dead_files() {
# NREad from standard-in and then check for any files
# that are no longer on the system and remove them
# from the list. Also note that the files in the list
# have been stripped of their first "/". Therefore,
# it has been added for the test.
while read -r FILE_IN
do
# Check if file exists and is readable. If not, do not archive.
if [[ -r "/${FILE_IN}" || -L "/${FILE_IN}" || -S "/${FILE_IN}" \
|| -p "/${FILE_IN}" || -b "/${FILE_IN}" || -c "/${FILE_IN}" \
|| -d "/${FILE_IN}" || -f "/${FILE_IN}" ]]; then
# The calling program accepts all output, so just do so.
print -r -- "${FILE_IN}"
else
print -r " /${FILE_IN}" >> ${TMP_GONE_FILE_LIST}
fi
done
} # End filter_dead_files()
Best regards...
Dietmar.
"Logic is the beginning of wisdom; not the end." -- Spock (Star Trek VI: The Undiscovered Country)
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.
News and Events
Support
© Copyright 2024 Hewlett Packard Enterprise Development LP