HPE GreenLake Administration
- Community Home
- >
- Servers and Operating Systems
- >
- Operating Systems
- >
- Operating System - HP-UX
- >
- must /var/adm/crash fileystem be in root VG?
Operating System - HP-UX
1825720
Members
2905
Online
109686
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
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
03-06-2000 05:34 AM
03-06-2000 05:34 AM
must /var/adm/crash fileystem be in root VG?
I am creating a separate filesystem for /var/adm/crash
but the current root vg has no free space. Is this
filesystem required to be in the root VG? I'm concerned
that other VGs may not be mounted/available at the point in the reboot where a
dump is being saved to
filesystem space.
+ Wayne
but the current root vg has no free space. Is this
filesystem required to be in the root VG? I'm concerned
that other VGs may not be mounted/available at the point in the reboot where a
dump is being saved to
filesystem space.
+ Wayne
2 REPLIES 2
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
03-06-2000 09:50 AM
03-06-2000 09:50 AM
Re: must /var/adm/crash fileystem be in root VG?
The default directory for crash dump is /var/adm/crash,
however you could specify a different directory. This directory could be within
a file system that doesn't belong to the volume group vg00. Only You have to
modify the file /etc/rc.config.d/savecore (using vi), the variable SAVECORE_DIR
indicate the directory where the system going to generate the dump.
Note: the filesystem in which this directory is located should have as much
free space as your system has RAM.
good luck!
however you could specify a different directory. This directory could be within
a file system that doesn't belong to the volume group vg00. Only You have to
modify the file /etc/rc.config.d/savecore (using vi), the variable SAVECORE_DIR
indicate the directory where the system going to generate the dump.
Note: the filesystem in which this directory is located should have as much
free space as your system has RAM.
good luck!
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
03-07-2000 07:14 PM
03-07-2000 07:14 PM
Re: must /var/adm/crash fileystem be in root VG?
You could just link the /var/adm/crash to another directory in another volume
group with more space. Just man the ln command. This saves messing with the
settings for dumping kernel at crash.
Rgds, Paul
group with more space. Just man the ln command. This saves messing with the
settings for dumping kernel at crash.
Rgds, Paul
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