- Community Home
- >
- Servers and Operating Systems
- >
- Operating Systems
- >
- Operating System - HP-UX
- >
- Additional dump device creation failure
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
тАО02-14-2006 02:50 PM
тАО02-14-2006 02:50 PM
Additional dump device creation failure
I was trying to create an additinal dump device on a 11i server. While trying to add it using crashconf -a I am getting the following error
crashconf -a
/dev/vg00/dump1: error: device is fully occupied by a file system
I have not created any filesystem on dump1. Following are the steps I did.
lvcreate -n dump1 -C y -r n /dev/vg00/dump1
lvextend -l 1650 /dev/vg00/dump1 /dev/dsk/c7t2d0
lvlnboot -d /dev/vg00/dump1
Added to /etc/fstab
/dev/vg00/dump1 ... dump defaults 0 0
crashconf -a
Thanks in advance,
Sudheer
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
тАО02-14-2006 04:55 PM
тАО02-14-2006 04:55 PM
Re: Additional dump device creation failure
Check using
# fstyp -v /dev/vg00/rdump1
you probably would see it has a FS. "crashconf -a" and "lvlnboot" as well won't work in such case.
As you are trying to add "additional" dump device, you should either use "lvlnboot -d" ( as you are adding in root vg ), reboot or use "crashconf -a" ( allows outside root vg device) to add on fly.
Be aware you may need to add "dump lvol" entry in the kernel if doesn't exist already.
# strings /stand/vmunix | grep "dump lvol"
If it is not there , then add "dump lvol" in /etc/system, rebuild kernel and reboot.
Refer manpages of lvlnboot and crashconf.
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
тАО02-14-2006 04:58 PM
тАО02-14-2006 04:58 PM
Re: Additional dump device creation failure
Wanted to add..
You can use dd command to wipe out the FS header/metadata from the dump1 lvol.
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
тАО02-14-2006 05:10 PM
тАО02-14-2006 05:10 PM
Re: Additional dump device creation failure
after these steps try
#lvlnboot -R ( just we trying update the Label File )
and take a copy of the kernel using the system_prep command and just check what is the entry in the file along with Dump parameter. if any change required change it
example : dump dump1
and create the new kernel and reboot it .
regards
Tvs
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
тАО02-14-2006 06:28 PM
тАО02-14-2006 06:28 PM
Re: Additional dump device creation failure
lvlnboot -v was showing the dump1 lvol also. But I was getting error on crashconf. fstyp was showing FS information, even though I have not created any file system on this lvol. I tried removing the lvol and recreating the same. but it was of no use.
dump lvol was there in kernel.
Finally what I did is, since this disk is used only as the dump device did a mediainit, followed the same steps in my original query, and it is showing in crashconf also.
Thanks for throwing the light.
Sudheer
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
тАО02-14-2006 07:40 PM
тАО02-14-2006 07:40 PM
Re: Additional dump device creation failure
The contents of previously used PVs in LVM are not overwritten if the new structure is created with similar parameters. This was probably the reason for this to happen. The disk was there in use earlier with LVM either on same of different system causing the LVM file system to appear without being created.
You would have been even surprised to see some data there if the file system was mounted.
Have a look at this interesting thread discussing this issue
http://forums1.itrc.hp.com/service/forums/questionanswers.do?threadId=1001334
HTH,
Devender
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
тАО02-14-2006 08:08 PM
тАО02-14-2006 08:08 PM
Re: Additional dump device creation failure
Thanks for the information. I was unable to access the link you provided
regards,
Sudheer
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
тАО02-14-2006 08:20 PM
тАО02-14-2006 08:20 PM
Re: Additional dump device creation failure
You can also get good information in "Recovery Handbook" in Chapter: Configuring Dump devices. I dont remember the chapter no# right now.
hth,
Raj.
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
тАО02-14-2006 08:38 PM
тАО02-14-2006 08:38 PM
Re: Additional dump device creation failure
http://forums1.itrc.hp.com/service/forums/questionanswer.do?threadId=1001334
In fact there was some problem with the earlier posting.
Best Regards,
Devender