- Community Home
- >
- Servers and Operating Systems
- >
- Legacy
- >
- Operating System - Tru64 Unix
- >
- system 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
тАО08-06-2005 02:48 PM
тАО08-06-2005 02:48 PM
system panic
Now the system crash often.There are lots of similar messages in the /var/adm/messages:
Aug 4 16:11:25 bssqub vmunix: ADVFS EXCEPTION
Aug 4 16:11:25 bssqub vmunix: Module = bs_sbm.c, Line = 337
Aug 4 16:11:25 bssqub vmunix: ADVFS INTERNAL ERROR: dealloc_bits_page: can't cl
ear a bit twice!
Aug 4 16:11:25 bssqub vmunix:
Aug 4 16:11:26 bssqub vmunix: panic (cpu 0): ADVFS INTERNAL ERROR: dealloc_bits
_page: can't clear a bit twice!
Aug 4 16:11:26 bssqub vmunix:
Aug 4 16:11:26 bssqub vmunix: syncing disks... 28 28 device string for dump = S
CSI 1 2 0 0 0 0 0.
Aug 4 16:11:26 bssqub vmunix: DUMP.prom: dev SCSI 1 2 0 0 0 0 0, block 1048576
Aug 4 16:11:26 bssqub vmunix: device string for dump = SCSI 1 2 0 0 0 0 0.
Aug 4 16:11:26 bssqub vmunix: DUMP.prom: dev SCSI 1 2 0 0 0 0 0, block 1048576
I use 'verify',but it does not work at all.What should I do?Please help me.Thank you
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
тАО08-06-2005 07:42 PM
тАО08-06-2005 07:42 PM
Re: system panic
Do you also have the fixfdmn command?
What os version are you running?
If you can mount the filesets in the domain, backup, recreate and restore the domain and filesets.
greetings,
Michael
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
тАО08-07-2005 07:01 AM
тАО08-07-2005 07:01 AM
Re: system panic
If you have filesystem problems that verify cannot fix, you may need to save the contents of the filesystem, recreate it and restore it.
Also, may be a physical disk problem, all errors points to the same SCSI dev.
What Tru64 version are you using:
sizer -v
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
тАО08-07-2005 05:22 PM
тАО08-07-2005 05:22 PM
Re: system panic
Please answer the following questions:
1.What is the OS version
2.Have you checked the SCSI Disk.
3.Please check the filesystem status you need to rebuild it.
4.Please run the verify command and if it is not working you need to use fixfdmn followed by the domain name.
Regards
manish
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
тАО08-07-2005 05:37 PM
тАО08-07-2005 05:37 PM