Simpler Navigation coming for Servers and Operating Systems
Coming soon: a much simpler Servers and Operating Systems section of the Community. We will combine many of the older boards, and you won't have to click through so many levels to get at the information you need. If you are looking for an older board and do not find it, check the consolidated boards, as the posts are still there.
Operating System - Tru64 Unix
cancel
Showing results for 
Search instead for 
Did you mean: 

hwmgr database

SOLVED
Go to solution
John Welsh_2
Regular Advisor

hwmgr database

Hi all,
In which file or files are the dsk numbers stored?
For example if I add a new disk it will be assigned the next available dsk number. eg: /dev/disk/dsk12c.
If I then shutdown, remove the disk and reboot and then do hwmgr -refresh scsi and hwmgr -refresh component, I would have thought that the reference to dsk12 has been removed. If I put the disk back and reboot, it now sees the disk as dsk13. I would expect that the dsk12 designation should have been available to be used again.
Where is this info stored ?
I guess I could use dsfmgr -m newname oldname but this is a bit messy.
Best Regards,
John Welsh.
===========
7 REPLIES
Ivan Ferreira
Honored Contributor

Re: hwmgr database

Hi, see the -I option in "man dsfmgr". I never used It.
Por que hacerlo dificil si es posible hacerlo facil? - Why do it the hard way, when you can do it the easy way?
Vladimir Fabecic
Honored Contributor

Re: hwmgr database

Hardware Component Databases:
/etc/dec_hwc_ldb Local (CDSL)
/etc/dec_hwc_cdb Cluster
/etc/dec_scsi_db Local (CDSL)
â ¢ Hardware Persistence Database:
/etc/dec_hw_db Local (CDSL)
â ¢ Device Special File Data Files
/etc/dfsl.dat Local (CDSL)
/etc/dfsc.dat Cluster
â ¢ Unique ID Database:
/etc/dec_unid_db Cluster
Things about devices are complicated, dsfmgr is tool to manage devices.
But if you removed a dsk12, shutdown, put it back and boot, you would see it as dsk12 again.
By the way what is your OS/patch version?
In vino veritas, in VMS cluster
Hein van den Heuvel
Honored Contributor

Re: hwmgr database

The goal/intend of Tru64 V5 (and better) is to have the same device come back as the same /dev/disk/dsk number.
This is based on the WWID of the device.

What Tru64 version?
What device?
Direct connect, or through smart controller?
What does 'Put the disk back' exactly mean?

>> I guess I could use dsfmgr -m newname oldname but this is a bit messy.

Not really. No big deal we did this as standard business practive for certain setups, just to please the eye.
For example, for one Oracle solution we had all redo as dsk1x, temp & undo on dsk2x, data drives as dsk3x and backup area as dsk4x.
We used a table to make it be just so, habitually blowing away the names Tru64 picked.

Be sure to carefully follow the man pages starting from dsfmgr

Cheers,
Hein.



As in


John Welsh_2
Regular Advisor

Re: hwmgr database

Hi Guys,

Thanks for your responses. What I was trying to achieve was to "reuse" a dsk number after a disk was removed and there was no chance that it would be reinstalled - eg: after it had died and been replaced. I expected that "hwmgr -refresh scsi" and "hwmgr -refresh component" would achieve that. When the replacement drive is plugged in it takes on the next dsk number and you have to rename it using dsfmgr -m.
As suggested I tried dsfmgr -I -v but this didn't seem to achieve anything, the dsk numbering still keeps on counting up.

I am running V5.1B PK4.

Also whats happened to the Tru64 on-line docs
and man pages ? I haven't been able to access them for a while.
Regards, John W.
=================


Steven Schweda
Honored Contributor

Re: hwmgr database

> Also whats happened to the Tru64 on-line
> docs and man pages ?

The Tru64 Web server's been dead since
Friday. Obviously a high priority at HP.

The forum system has been doing about as well
as usual lately, too.
DCBrown
Frequent Advisor
Solution

Re: hwmgr database

Using dsfmgr -I should have worked. I routinely use it. See attached for an example. This example was on a V5.1B/BL26 system (PK5?).

Of course this only works for the highest numbered disk. Tru64 won't find holes in the dsk numbering scheme and use those. So for all disks other than the highest numbered one you really need to use hwmgr delete/move functionality.

John Welsh_2
Regular Advisor

Re: hwmgr database

Thanks to all who helped.
I have assigned points.
John Welsh.
============