- Community Home
- >
- Servers and Operating Systems
- >
- Legacy
- >
- Operating System - Tru64 Unix
- >
- Re: Domain panic
Operating System - Tru64 Unix
1752764
Members
4733
Online
108789
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
Discussions
Discussions
Forums
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
Discussion Boards
Discussion Boards
Blogs
Information
Community
Resources
Community Language
Language
Forums
Blogs
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
тАО10-11-2010 11:40 PM
тАО10-11-2010 11:40 PM
Domain panic
Hi Gurus,
One domain is paniced and filesets are not mounted. Other domain and filesets are working fine. Plz suggest.
# /sbin/voldctl no enable
lsm:voldctl: ERROR: Cannot open /dev/volinfo: No such file or directory
# /sbin/vold
lsm:vold: ERROR: cannot open /dev/volconfig: No such file or directory
# /usr/sbin/volinfo
lsm:volinfo: ERROR: IPC failure: Configuration daemon is not accessible
Jul 31 08:15:13 host1 vmunix: Found bad xor in sbm_total_free_space! Corrupted SBM metadata file!
Jul 31 08:15:13 host1 vmunix:
Jul 31 08:15:13 host1 vmunix: AdvFS Domain Panic; Domain oracle_dmn Id 0x3a14fa5c.00013a5e
Jul 31 08:15:13 host1 vmunix: An AdvFS domain panic has occurred due to either a metadata write error or an internal inconsistency. This domain is being rendered inaccessible.
Jul 31 08:15:13 host1 vmunix: Please refer to guidelines in AdvFS Guide to File System Administration regarding what steps to take to recover this domain.
Jul 31 08:15:13 host1 vmunix:
Sep 24 15:53:33 host1 vmunix: Incorrect tag (0.0) in mcell. Expected 6bd6.8002.
Sep 24 15:53:33 host1 vmunix: AdvFS Domain Panic; Domain oracle_dmn Id 0x3a14fa5c.00013a5e
Sep 24 15:53:33 host1 vmunix: An AdvFS domain panic has occurred due to either a metadata write error or an internal inconsistency. This domain is being rendered inaccessible.
Sep 24 15:53:33 host1 vmunix: Please refer to guidelines in AdvFS Guide to File System Administration regarding what steps to take to recover this domain.
One domain is paniced and filesets are not mounted. Other domain and filesets are working fine. Plz suggest.
# /sbin/voldctl no enable
lsm:voldctl: ERROR: Cannot open /dev/volinfo: No such file or directory
# /sbin/vold
lsm:vold: ERROR: cannot open /dev/volconfig: No such file or directory
# /usr/sbin/volinfo
lsm:volinfo: ERROR: IPC failure: Configuration daemon is not accessible
Jul 31 08:15:13 host1 vmunix: Found bad xor in sbm_total_free_space! Corrupted SBM metadata file!
Jul 31 08:15:13 host1 vmunix:
Jul 31 08:15:13 host1 vmunix: AdvFS Domain Panic; Domain oracle_dmn Id 0x3a14fa5c.00013a5e
Jul 31 08:15:13 host1 vmunix: An AdvFS domain panic has occurred due to either a metadata write error or an internal inconsistency. This domain is being rendered inaccessible.
Jul 31 08:15:13 host1 vmunix: Please refer to guidelines in AdvFS Guide to File System Administration regarding what steps to take to recover this domain.
Jul 31 08:15:13 host1 vmunix:
Sep 24 15:53:33 host1 vmunix: Incorrect tag (0.0) in mcell. Expected 6bd6.8002.
Sep 24 15:53:33 host1 vmunix: AdvFS Domain Panic; Domain oracle_dmn Id 0x3a14fa5c.00013a5e
Sep 24 15:53:33 host1 vmunix: An AdvFS domain panic has occurred due to either a metadata write error or an internal inconsistency. This domain is being rendered inaccessible.
Sep 24 15:53:33 host1 vmunix: Please refer to guidelines in AdvFS Guide to File System Administration regarding what steps to take to recover this domain.
- Tags:
- panic
3 REPLIES 3
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
тАО10-12-2010 07:59 AM
тАО10-12-2010 07:59 AM
Re: Domain panic
Hi,
What's the hardware configuration ?
What OS ?
Domain panics are usually caused by some form of hardware issue, but knowing nothing about your setup it's very difficult to offer any advice.
Regards,
Rob
What's the hardware configuration ?
What OS ?
Domain panics are usually caused by some form of hardware issue, but knowing nothing about your setup it's very difficult to offer any advice.
Regards,
Rob
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
тАО10-19-2010 12:46 AM
тАО10-19-2010 12:46 AM
Re: Domain panic
hi,
OSF1 srvr1 V5.0 910 alpha
DS 20 Alpha
OSF1 srvr1 V5.0 910 alpha
DS 20 Alpha
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
тАО10-19-2010 01:19 AM
тАО10-19-2010 01:19 AM
Re: Domain panic
Hi,
I still know nothing of your hardware configuration...
The output of the following commands might help:
# sizer -v
# hwmgr view hier
# hwmgr view dev
Cheers,
Rob
I still know nothing of your hardware configuration...
The output of the following commands might help:
# sizer -v
# hwmgr view hier
# hwmgr view dev
Cheers,
Rob
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.
News and Events
Support
© Copyright 2024 Hewlett Packard Enterprise Development LP