pax: dev/klog : > 2GB. Not Dumped.

[Pete Randall]

First boot will do an "insf -e" to install all the device files anyway.


Pete

[Pierre Samson]

I'm worried that the system would rebuild the devices files as it please. I had a bad experience with Solaris. It associated devices to differents disk.
I would not want that it takes a 9Gig drive and make it /dev/dsk/c0t2d0 when previously (at time of the backup) this was a 18Gig, it would be a mess.

[Sridhar Bhaskarla]

Hi Pete,

Thanks for the greetings. It's a different world to me right now ;-).

We have this patch installed on all our boxes. From the following -

( SR:8606196471 CR:JAGad65674 )
Enhancement request: pax(1) is enhanced to support the
archival of files up to 8GB in USTAR format from 2GB.
The command tar(1) is upgraded to support the archival of
files up to 8GB as well.

It is hard to believe HP would do something like what Steven encountered. We didn't run into this kind of scenarios so far.



-Sri

[Sridhar Bhaskarla]

Hi Pierre,

'insf -e' is safe to run to recreate the missing device files. If it is not safe, then the HP-UX administrators would always be busy doing vgexport/vgimport, vgcfgrestores and vgscans.

-Sri

[Pierre Samson]

Cool, I'll use it as the last resort.
I'd really like to have my device file backup as they are. Is it possible from ignite or pax will always get mixed up.

[Sridhar Bhaskarla · Accepted solution]

Hi,

You should get your old device files back. However, it is not 100% guaranteed. I read sometime back certain scenarios where the instance numbers may change during the recovery. One of it is due to a bad ioscan patch. I do not recall the patch number. The other case that I personally encountered was if I removed the cables to the disk system during the recovery process. You can always get the desired instance numbers by using the "ioinit" command. It came handy to me quite sometimes.

-Sri