Clean an LV out of the ODM


 
Thread Tools Search this Thread
Top Forums UNIX for Advanced & Expert Users Clean an LV out of the ODM
# 1  
Old 11-23-2004
Clean an LV out of the ODM

I recently had a disk crash and was not able to clean the dump lv off the disk. Now trying to create new lvdump I am running into errors.
My question is how do I remove the old lv out of the ODM? I have tried going through smit and also just rmlv and it cannot find the lv. Yet when I run lslv on lvdump it shows up.

Thanks
Login or Register to Ask a Question

Previous Thread | Next Thread

10 More Discussions You Might Find Interesting

1. AIX

AIX Migration issue with EMC ODM sets

Hi Experts , I want to start migrating our AIX 6.1 to AIX 7.1 . I am planning to use alt_disk_migration . Chris gibson has awesome documentation in the internet. However I am running into an issue with EMC odm filesets . So my current OS is AIX 6.1. and I have this : lslpp -l | grep EMC ... (7 Replies)
Discussion started by: JME2015
7 Replies

2. AIX

How to add the attribute to odm if it contains negative value?

Hi All, I am trying to add odm_wait attribute to CuAt programatically using putattr(&pCuAt). I was able to add when the odm_wait has positive value . But, I am facing issues when the odm_wait has negative value As per IBM, these are the odm_wait possible values #define ODM_WAIT -1 /*... (3 Replies)
Discussion started by: Sachin1987
3 Replies

3. AIX

Removing object from ODM base

Hello! I did a big mistake and now I have to change the ODM base manually :wall: I had a server of test with 2 VG (rootvg and datavg). I had to test something on it with an other AIX version. So, to be sure to restore it, i did a mksysb before but I had completly forgotten the second vg and... (1 Reply)
Discussion started by: Castelior
1 Replies

4. AIX

Problem with the ODM base

Hi, I gonna try to explain my problem. When I list my tty I have something like that: sa3 is the RAN where the tty are connected. Yesterday I tried to delete every tty from the RAN I had a problem with a tty which was not possible to delete with rmdev -dl, so I had to : - delete it... (0 Replies)
Discussion started by: Castelior
0 Replies

5. AIX

remove default gateway on ODM

Hi All, I remove the default gateway by using a command line but I need also to remove it from ODM so that reboot will not trigger it back. How do I remove it from ODM of AIX 5.3? Thanks for any comment you may add. (4 Replies)
Discussion started by: itik
4 Replies

6. AIX

How to clean PV id?

When I run command: >chdev -l hdisk1 -a pv=clear It shows Method error (/etc/methods/chgdisk): 0514-062 Cannot perform the requested function because the specified device is busy. run: #>fuser -kxuc /dev/raw1 /dev/raw1: How to clean PV id? (4 Replies)
Discussion started by: rainbow_bean
4 Replies

7. AIX

Odm & Lvm

Can i have BIG help on ODM and LVM??? I m new to AIX..... Devang (2 Replies)
Discussion started by: 10aix
2 Replies

8. AIX

Script for Comparing VGDA and ODM

Hi there guys, if you have already this script as this will help us in determining of the two are consistent, and if it is not, which is the one correct. Hope you also have for this one.:) (1 Reply)
Discussion started by: sky_lark02
1 Replies

9. AIX

Removing devices from ODM

I have replace a couple of hdisks in and old AIX 4 system. I have them assigned to the hdisk numbers previously in the system. When I don an lsvg -p vgname, i see them old devices by device number still come up as missing. I think they are still in the ODM,, how can I remove them? Thanks Mike (5 Replies)
Discussion started by: mhenryj
5 Replies

10. UNIX Benchmarks

ocs_vtsup: error locking odm database

Someone know something about this error ? We have 5.2 and HACMP Cluster. (1 Reply)
Discussion started by: hjara
1 Replies
Login or Register to Ask a Question
savecore(1M)                                              System Administration Commands                                              savecore(1M)

NAME
savecore - save a crash dump of the operating system SYNOPSIS
/usr/bin/savecore [-Lvd] [-f dumpfile] [directory] DESCRIPTION
The savecore utility saves a crash dump of the kernel (assuming that one was made) and writes a reboot message in the shutdown log. It is invoked by the dumpadm service each time the system boots. savecore saves the crash dump data in the file directory/vmcore.n and the kernel's namelist in directory/unix.n. The trailing .n in the pathnames is replaced by a number which grows every time savecore is run in that directory. Before writing out a crash dump, savecore reads a number from the file directory/minfree. This is the minimum number of kilobytes that must remain free on the file system containing directory. If after saving the crash dump the file system containing directory would have less free space the number of kilobytes specified in minfree, the crash dump is not saved. if the minfree file does not exist, savecore assumes a minfree value of 1 megabyte. The savecore utility also logs a reboot message using facility LOG_AUTH (see syslog(3C)). If the system crashed as a result of a panic, savecore logs the panic string too. OPTIONS
The following options are supported: -d Disregard dump header valid flag. Force savecore to attempt to save a crash dump even if the header information stored on the dump device indicates the dump has already been saved. -f dumpfile Attempt to save a crash dump from the specified file instead of from the system's current dump device. This option may be useful if the information stored on the dump device has been copied to an on-disk file by means of the dd(1M) command. -L Save a crash dump of the live running Solaris system, without actually rebooting or altering the system in any way. This option forces savecore to save a live snapshot of the system to the dump device, and then immediately to retrieve the data and to write it out to a new set of crash dump files in the specified directory. Live system crash dumps can only be per- formed if you have configured your system to have a dedicated dump device using dumpadm(1M). savecore -L does not suspend the system, so the contents of memory continue to change while the dump is saved. This means that live crash dumps are not fully self-consistent. -v Verbose. Enables verbose error messages from savecore. OPERANDS
The following operands are supported: directory Save the crash dump files to the specified directory. If directory is not specified, savecore saves the crash dump files to the default savecore directory, configured by dumpadm(1M). FILES
directory/vmcore.n directory/unix.n directory/bounds directory/minfree /var/crash/'uname -n' default crash dump directory ATTRIBUTES
See attributes(5) for descriptions of the following attributes: +-----------------------------+-----------------------------+ | ATTRIBUTE TYPE | ATTRIBUTE VALUE | +-----------------------------+-----------------------------+ |Availability |SUNWcsu | +-----------------------------+-----------------------------+ SEE ALSO
adb(1), mdb(1), svcs(1), dd(1M), dumpadm(1M), svcadm(1M), syslog(3C), attributes(5), smf(5) NOTES
The system crash dump service is managed by the service management facility, smf(5), under the service identifier: svc:/system/dumpadm:default Administrative actions on this service, such as enabling, disabling, or requesting restart, can be performed using svcadm(1M). The ser- vice's status can be queried using the svcs(1) command. If the dump device is also being used as a swap device, you must run savecore very soon after booting, before the swap space containing the crash dump is overwritten by programs currently running. SunOS 5.10 25 Sep 2004 savecore(1M)