Operating System - HP-UX
1748136 Members
3741 Online
108758 Solutions
New Discussion

Re: make_tape_recovery completed unsuccessfully

 
SOLVED
Go to solution
Torsten.
Acclaimed Contributor
Solution

Re: make_tape_recovery completed unsuccessfully

After some google around I found this:

In /opt/ignite/bin/make_medialif

change LIFVolSize='500000000' to LIFVolSize='750000000'.

there is obviously not enough space in the defined LIF area to hold all the files.


Hope this helps!
Regards
Torsten.

__________________________________________________
There are only 10 types of people in the world -
those who understand binary, and those who don't.

__________________________________________________
No support by private messages. Please ask the forum!

If you feel this was helpful please click the KUDOS! thumb below!   
EU-Admins-UNIX
Regular Advisor

Re: make_tape_recovery completed unsuccessfully

I will try this, but I have checked other working systems, and the parameter is 500000000.  I'll let you know how it goes.

 

Regards

 

Tariq

EU-Admins-UNIX
Regular Advisor

Re: make_tape_recovery completed unsuccessfully

It's got past the problem stage, and is still running.  I'll let you know the outcome.

 

I'll be sure to add points!

 

Thanks

 

Tariq

EU-Admins-UNIX
Regular Advisor

Re: make_tape_recovery completed unsuccessfully

Great, it worked!

 

But I still have a query. 

 

When validating the archive with tar tvf

 

I do the ...... fsf 1 etc

 

But can only read the archive with

 

tar tvf /dev/rmt/4mn, it doesn;t work with tar tvf /dev/rmt/4m

 

See below:

 

# mt -f /dev/rmt/4m rew
# mt -f /dev/rmt/4m fsf 1
# tar tvf /dev/rmt/4m
Tar: blocksize = 4
directory checksum error

 

And:

 

#  mt -f /dev/rmt/4m rew
# mt -f /dev/rmt/4mn fsf 1
# tar tvf /dev/rmt/4mn
r-xr-xr-x   2/2      0 Jan 31 08:24 2012 stand/
rwxr-xr-x   0/0      0 Jan 19 10:10 2012 stand/lost+found/
rw-r--r--   0/3   5260 Jan 31 11:52 2012 stand/ioconfig
rw-r--r--   0/3  11008 Jan 31 11:52 2012 stand/ext_ioconfig
rw-r--r--   0/3     19 Jan 19 10:11 2012 stand/bootconf
rwxr-xr-x   0/0      0 Jan 31 08:23 2012 stand/system symbolic link to nextboot/system
rw-r--r--   0/3      0 Jan 19 10:21 2012 stand/.kc.lock
rwxr-xr-x   0/3      0 Jan 31 08:25 2012 stand/krs/
rw-r--r--   0/0   4584 Jan 31 08:25 2012 stand/krs/system.krs
rw-r--r--   0/0   4584 Jan 30 12:45 2012 stand/krs/system.krs.lkg
rwxr-xr-x   0/0      0 Jan 31 08:24 2012 stand/nextboot symbolic link to current
rwxr-xr-x   0/0      0 Jan 31 08:23 2012 stand/bootfs symbolic link to current/bootfs
rwxr-xr-x   0/3      0 Jan 19 11:26 2012 stand/current/

 

Regards

 

Tariq

Patrick Wallek
Honored Contributor

Re: make_tape_recovery completed unsuccessfully

When you used the device file /dev/rmt/4m you used the device that WILL rewind the drive after it finishes its action. So when you did 'mt -f /dev/rmt/4m fsf 1' it moved the tape forward 1 file as you asked, but since you used 4m it rewound the tape when it finished.

 

This is why you must use the 4mn device file.  The 'n' at the end means no-rewind.  So when you do 'mt -f /dev/rmt/4mn fsf 1' it will move the tape forward 1 file and stop at that point.  That is where the 'tar' portion of the tape starts.

Torsten.
Acclaimed Contributor

Re: make_tape_recovery completed unsuccessfully

Not working:

# mt -f /dev/rmt/4m fsf 1

working:

# mt -f /dev/rmt/4mn fsf 1

You need to use the no-rewind device file ("n").

Hope this helps!
Regards
Torsten.

__________________________________________________
There are only 10 types of people in the world -
those who understand binary, and those who don't.

__________________________________________________
No support by private messages. Please ask the forum!

If you feel this was helpful please click the KUDOS! thumb below!   
EU-Admins-UNIX
Regular Advisor

Re: make_tape_recovery completed unsuccessfully

Thanks Patrick

 

Makes sense!