- Community Home
- >
- Servers and Operating Systems
- >
- Operating Systems
- >
- Operating System - HP-UX
- >
- /var/adm/crash and partitioning during install
Operating System - HP-UX
1756823
Members
3621
Online
108853
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
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
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
09-19-2006 05:19 AM
09-19-2006 05:19 AM
We have 32GB of physical memory and the system install CD wants us to allocate 32+ GB's of our 72GB drives to support crash dumps.
Questions:
1.) Is it supported to mount a SAN drive to /var/adm/crash to collect potential dumps?
2.) If so, will the system still boot if the SAN isn't available (and /var/adm/crash cannot be mounted)?
Do I need to allocate 16GB to swap+dump also??? I should never be swapping and only have minimal paging.
I want to do this (any issues):
/stand -> 1
/ --> 4
/home --> 8
/usr --> 12
/var --> 12
/opt --> 12
swap+dump -> 16
/tmp --> 2
And mount SAN disk to /var/adm/crash maybe? Tell me I'm crazy, if it is so. What would you do?
Questions:
1.) Is it supported to mount a SAN drive to /var/adm/crash to collect potential dumps?
2.) If so, will the system still boot if the SAN isn't available (and /var/adm/crash cannot be mounted)?
Do I need to allocate 16GB to swap+dump also??? I should never be swapping and only have minimal paging.
I want to do this (any issues):
/stand -> 1
/ --> 4
/home --> 8
/usr --> 12
/var --> 12
/opt --> 12
swap+dump -> 16
/tmp --> 2
And mount SAN disk to /var/adm/crash maybe? Tell me I'm crazy, if it is so. What would you do?
Solved! Go to Solution.
1 REPLY 1
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
09-19-2006 05:27 AM
09-19-2006 05:27 AM
Solution
only down side of /var/adm/crash being on SAN that I can see is, if your SAN attachment channel, let it be SCSI or fiberoptic, induces a panic, you may not be able to get a dump to analyze.
As far as the size of the crash area goes, quarter of the size of physical memory should be enough to capture what will help you to analyze the crash. After all you are only interested in the OS area in memory when a crash happens 99.9% of the time. Also consider that the dump, when it is written to the disk, is compressed quite a bit. So 1/4th of actual physical memory is quite generous allocation in my opinion on today's large memory systems.
As far as the size of the crash area goes, quarter of the size of physical memory should be enough to capture what will help you to analyze the crash. After all you are only interested in the OS area in memory when a crash happens 99.9% of the time. Also consider that the dump, when it is written to the disk, is compressed quite a bit. So 1/4th of actual physical memory is quite generous allocation in my opinion on today's large memory systems.
________________________________
UNIX because I majored in cryptology...
UNIX because I majored in cryptology...
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