HPE GreenLake Administration
- Community Home
- >
- Servers and Operating Systems
- >
- Operating Systems
- >
- Operating System - HP-UX
- >
- Mirror Break
Operating System - HP-UX
1825733
Members
2850
Online
109687
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
Forums
Discussions
Discussions
Discussions
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
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
01-05-2006 05:09 AM
01-05-2006 05:09 AM
Hello all..
sorry to put SUN query here..
i dont know the SUN forum URL.
At the mo we have 3 state db's on slice 7 of c0t0d0 disk, we should have had 3 copies on c0t1d0 (the mirror)
We have lost c0t0d0 (the format command is reporting the disk as not available) which means we have lost the mirrors db's.
the OS is up (just) as it is running on the mirror, but because there are no dbs to record any transactions to, the stability of the OS is compromised.
A reboot will loose us both disks!, we considered trying to back up the disk whilst it is still up, but as the loss of the db's is interfering with the operating systems stability, we are sure that any backup taken would be corrupted.
The only real option available would be to rebuild the server from scratch. this would ensure a clean and stable platform for integration.
I am also making changes to the Jumpstart server to ensure that this problem is not inherent in future builds.
some work will need to be done to also protect the other pits3 servers from the same fate.
5. Creating State Database :
State meta database , metadb , keeps information of the metadevices and is needed for Disksuite operation . Disksuite can not function without metadb so a copy of replica databases is placed on different disks to ensure that a copy is available in case of a complete disk failure .
Metadb needs a dedicated disk slice so create partitions of about 5 Meg. on the disks for metadb. If there is no space available for metadb then it can be taken from swap . Having metadb on two disks can create problems as DISKSUITE looks for database replica number > 50% of total replicas and if one of the two disks crashes the replica falls at 50% . On next reboot system will go to single user mode and one has to recreate additional replicas to correct the metadb errors.
The following command creates three replicas of metadb on three disk slices.
#metadb -a -f -c 3 /dev/dsk/c0t1d0s6 /dev/dsk/c0t2d0s6 /dev/dsk/c0t3d0s6
+++++++++++++++++++++++++++++++++++++++++++++++
I WILL BE VERY THANKSFUL IF ANYONE GIVES ME SOLUTION FOR THIS....
if not ossible in SUN, how would have overcome if the same problem comes in hpux
eagerly waiting for replies
yogesh
sorry to put SUN query here..
i dont know the SUN forum URL.
At the mo we have 3 state db's on slice 7 of c0t0d0 disk, we should have had 3 copies on c0t1d0 (the mirror)
We have lost c0t0d0 (the format command is reporting the disk as not available) which means we have lost the mirrors db's.
the OS is up (just) as it is running on the mirror, but because there are no dbs to record any transactions to, the stability of the OS is compromised.
A reboot will loose us both disks!, we considered trying to back up the disk whilst it is still up, but as the loss of the db's is interfering with the operating systems stability, we are sure that any backup taken would be corrupted.
The only real option available would be to rebuild the server from scratch. this would ensure a clean and stable platform for integration.
I am also making changes to the Jumpstart server to ensure that this problem is not inherent in future builds.
some work will need to be done to also protect the other pits3 servers from the same fate.
5. Creating State Database :
State meta database , metadb , keeps information of the metadevices and is needed for Disksuite operation . Disksuite can not function without metadb so a copy of replica databases is placed on different disks to ensure that a copy is available in case of a complete disk failure .
Metadb needs a dedicated disk slice so create partitions of about 5 Meg. on the disks for metadb. If there is no space available for metadb then it can be taken from swap . Having metadb on two disks can create problems as DISKSUITE looks for database replica number > 50% of total replicas and if one of the two disks crashes the replica falls at 50% . On next reboot system will go to single user mode and one has to recreate additional replicas to correct the metadb errors.
The following command creates three replicas of metadb on three disk slices.
#metadb -a -f -c 3 /dev/dsk/c0t1d0s6 /dev/dsk/c0t2d0s6 /dev/dsk/c0t3d0s6
+++++++++++++++++++++++++++++++++++++++++++++++
I WILL BE VERY THANKSFUL IF ANYONE GIVES ME SOLUTION FOR THIS....
if not ossible in SUN, how would have overcome if the same problem comes in hpux
eagerly waiting for replies
yogesh
There is never a wrong time to do the right things
Solved! Go to Solution.
1 REPLY 1
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
01-05-2006 05:31 AM
01-05-2006 05:31 AM
Solution
Do I understand you correctly that there are no state db's on the good disk (c0t1d0)? Is there a slice avaiable for a state db (c0t1d0s7)?
If you run "metadb -i" and "metastat", what do the output of those show?
I seems like you should be able to run "metadb -a -f -c 3 /dev/dsk/c0t1d0s7" and create state db's on the good disk.
If you run "metadb -i" and "metastat", what do the output of those show?
I seems like you should be able to run "metadb -a -f -c 3 /dev/dsk/c0t1d0s7" and create state db's on the good disk.
Link down -- cable problem?
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.
Company
Support
Events and news
Customer resources
© Copyright 2025 Hewlett Packard Enterprise Development LP