- Community Home
- >
- Servers and Operating Systems
- >
- Legacy
- >
- Operating System - Tru64 Unix
- >
- Re: Domain Panic
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
тАО11-03-2009 02:55 AM
тАО11-03-2009 02:55 AM
Hello,
We have a TRU64 host with few domains created. It has the external disk array as well connected via SCSI cables.
one of the admins , accidently removed the scsi connectors from the external disk and that made one of the domain
as inaccessible. Domain Panic. The domain has some data files in it so the server is still up.
Now the question is , in order to bring the system to the previous stage, if we shutdown the host and connected
the cables as before and then start up the host, will the system take up??
I am thinking of hash out the domain entry from /etc/fstab and then bring the system up and then try to
mount the domains/shares one by one.
Kindly suggest at the earliest.
Thanx,
admin
Solved! Go to Solution.
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
тАО11-03-2009 03:04 AM
тАО11-03-2009 03:04 AM
Re: Domain Panic
One more update, we have found the below error in messages file,
Nov 3 11:22:04 SERVER1 vmunix: io/vol.c(volerror): Uncorrectable write error on volume vol_source, plex pl-02, block 24101008
Nov 3 11:22:04 SERVER1 vmunix: io/vol.c(volerror): Uncorrectable write error on volume vol_source, plex pl-01, block 24101008
Nov 3 11:22:04 SERVER1 vmunix: io/vol.c(volerror): Uncorrectable write error on volume vol_source, plex pl-02, block 17776
Nov 3 11:22:04 SERVER1 vmunix: io/vol.c(volerror): Uncorrectable write error on volume vol_source, plex pl-01, block 17776
Nov 3 11:22:05 SERVER1 vmunix: voliod_error: plex detach - volume vol_source, plex pl-01
Nov 3 11:22:05 SERVER1 vmunix: AdvFS I/O error:
Nov 3 11:22:05 SERVER1 vmunix: Domain#Fileset: source_domain#util
Nov 3 11:22:05 SERVER1 vmunix: Mounted on: /tools
Nov 3 11:22:05 SERVER1 vmunix: Volume: /dev/vol/sourcedg/vol_source
Nov 3 11:22:05 SERVER1 vmunix: Tag: 0x000198be.8007
Nov 3 11:22:05 SERVER1 vmunix: Page: 304
Nov 3 11:22:06 SERVER1 vmunix: Block: 24101008
Nov 3 11:22:06 SERVER1 vmunix: Block count: 16
Nov 3 11:22:06 SERVER1 vmunix: Type of operation: Write
Nov 3 11:22:06 SERVER1 vmunix: Error: 5
Nov 3 11:22:06 SERVER1 vmunix: To obtain the name of the file on which
Nov 3 11:22:06 SERVER1 vmunix: the error occurred, type the command:
Nov 3 11:22:06 SERVER1 vmunix: /sbin/advfs/tag2name /tools/.tags/104638
Nov 3 11:22:06 SERVER1 vmunix: AdvFS I/O error:
Nov 3 11:22:06 SERVER1 vmunix: Volume: /dev/vol/sourcedg/vol_source
Nov 3 11:22:06 SERVER1 vmunix: Tag: 0xfffffff7.0000
Nov 3 11:22:06 SERVER1 vmunix: Page: 289
Nov 3 11:22:06 SERVER1 vmunix: Block: 17776
Nov 3 11:22:06 SERVER1 vmunix: Block count: 16
Nov 3 11:22:06 SERVER1 vmunix: Type of operation: Write
Nov 3 11:22:06 SERVER1 vmunix: Error: 5
Nov 3 11:22:06 SERVER1 vmunix:
Nov 3 11:22:06 SERVER1 vmunix: bs_osf_complete: metadata write failed
Nov 3 11:22:06 SERVER1 vmunix: AdvFS Domain Panic; Domain source_domain Id 0x36fbab0b.000d26ec
Nov 3 11:22:06 SERVER1 vmunix: An AdvFS domain panic has occurred due to either a metadata write error or an internal inconsistency. This domain is being ren
dered inaccessible.
Nov 3 11:22:06 SERVER1 vmunix: Please refer to guidelines in AdvFS Guide to File System Administration regarding what steps to take to recover this domain.
Thanx,
admin
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
тАО11-03-2009 03:33 AM
тАО11-03-2009 03:33 AM
Re: Domain Panic
If its only related to SCSi connector, i don think you need to hash out /etc/fstab.
But its good idea.
BR,
Kapil+
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
тАО11-03-2009 03:44 AM
тАО11-03-2009 03:44 AM
Re: Domain Panic
But the problem is , when I try to access any share I get,
# cd /opt
ksh[6]: /opt: permission denied
So looks like something we need to do to remap the domain.
We use LSM.
Thanx.
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
тАО11-03-2009 07:14 AM
тАО11-03-2009 07:14 AM
Re: Domain Panic
Any help would be appreciated.
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
тАО11-03-2009 09:56 PM
тАО11-03-2009 09:56 PM
Re: Domain Panic
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
тАО11-03-2009 10:24 PM
тАО11-03-2009 10:24 PM
Re: Domain Panic
Getting following error for the said domain,
# showfdmn source_domain
showfdmn: unable to get info for domain 'source_domain'
showfdmn: error = I/O error
Thanx
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
тАО11-04-2009 05:38 AM
тАО11-04-2009 05:38 AM
Re: Domain Panic
voldctl disable and enable it again.
and check if thats not working
just try to export and import dg
BR,
Kapil+
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
тАО11-04-2009 05:42 AM
тАО11-04-2009 05:42 AM
Re: Domain Panic
# voldg list
NAME STATE ID
rootdg enabled 966101943.1025.bwgb550.vt.siemens.de
sourcedg disabled 1007210557.3627.bwgb550.vt.siemens.de
dokudg enabled 940102215.1973.bwgb550.vt.siemens.de
toolsdg enabled 944403128.1335.bwgb550.vt.siemens.de
If I do voldg disable command , will it affect any of the working dgs...i mean it should not ...as it also has rootdg in it.
So concerned.
If disable/enable do not work. Can you please give me the further steps to import/deport
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
тАО11-04-2009 05:54 AM
тАО11-04-2009 05:54 AM
Re: Domain Panic
i would suggest
export dg
voldctl disable/enable
import dg
Should work!!
Only touch affected dg nothing would happen :)
BR,
Kapil+