- Community Home
- >
- Servers and Operating Systems
- >
- Legacy
- >
- Operating System - Tru64 Unix
- >
- Re: hwmgr database
Categories
Company
Local Language
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
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
Community
Resources
Forums
Blogs
- 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-14-2007 07:42 PM
тАО06-14-2007 07:42 PM
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.
===========
Solved! Go to Solution.
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
тАО06-14-2007 09:54 PM
тАО06-14-2007 09:54 PM
Re: hwmgr database
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
тАО06-15-2007 08:38 PM
тАО06-15-2007 08:38 PM
Re: hwmgr database
/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?
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
тАО06-16-2007 12:16 AM
тАО06-16-2007 12:16 AM
Re: hwmgr database
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
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
тАО06-18-2007 12:38 PM
тАО06-18-2007 12:38 PM
Re: hwmgr database
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.
=================
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
тАО06-18-2007 06:22 PM
тАО06-18-2007 06:22 PM
Re: hwmgr database
> 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.
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
тАО06-19-2007 05:54 AM
тАО06-19-2007 05:54 AM
SolutionOf 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.
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
тАО07-09-2007 01:12 PM
тАО07-09-2007 01:12 PM
Re: hwmgr database
I have assigned points.
John Welsh.
============