02-28-2008
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.
10 More Discussions You Might Find Interesting
1. UNIX for Advanced & Expert Users
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... (0 Replies)
Discussion started by: Wamland
0 Replies
2. UNIX Benchmarks
Someone know something about this error ?
We have 5.2 and HACMP Cluster. (1 Reply)
Discussion started by: hjara
1 Replies
3. AIX
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
4. AIX
Can i have BIG help on ODM and LVM???
I m new to AIX.....
Devang (2 Replies)
Discussion started by: 10aix
2 Replies
5. AIX
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. Shell Programming and Scripting
Hi,
My below output file looks like this.
Backup status at Tue Jul 7 03:30:07 EDT 2009 CMLP
Job Name Last Start Last End ST Run Pri/Xit
____________________________ ____________________ ____________________ __ _______ ___
tnx415uu 07/06/2009 22:01:41 ----- RU 5547800/1
tnp415uu 07/06/2009... (2 Replies)
Discussion started by: intiraju
2 Replies
7. AIX
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
8. AIX
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
9. AIX
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
10. AIX
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
LEARN ABOUT SUNOS
pthread_mutex_consistent_np
pthread_mutex_consistent_np(3C) pthread_mutex_consistent_np(3C)
NAME
pthread_mutex_consistent_np - make a mutex consistent after owner death
SYNOPSIS
cc -mt [ flag... ] file... -lpthread [ library... ]
#include <pthread.h>
int pthread_mutex_consistent_np(pthread_mutex_t *mutex);
The following applies only if the symbol _POSIX_THREAD_PRIO_INHERIT is defined, and for mutexes that have been initialized with the proto-
col attribute having the value PTHREAD_PRIO_INHERIT. See pthread_mutexattr_getprotocol(3C).
The mutex object referenced by mutex is made consistent by calling pthread_mutex_consistent_np().
A consistent mutex becomes inconsistent and is unlocked if its owner dies while holding it. A subsequent owner of the mutex will acquire
the mutex with pthread_mutex_lock(3C), which will return EOWNERDEAD to indicate that the acquired mutex is inconsistent.
The pthread_mutex_consistent_np() function should be called while holding the mutex acquired by a previous call to pthread_mutex_lock()that
returned EOWNERDEAD.
Since the critical section protected by the mutex could have been left in an inconsistent state by the dead owner, the caller should make
the mutex consistent only if it is able to make the critical section protected by the mutex consistent.
Calls to pthread_mutex_lock(), pthread_mutex_unlock(), and pthread_mutex_trylock() for a consistent mutex will behave in the normal manner.
The behavior of pthread_mutex_consistent_np() for a mutex which is not inconsistent, or which is not held, is undefined.
Upon successful completion, the pthread_mutexattr_consistent_np() function returns 0. Otherwise, an error number is returned to indicate
the error.
The pthread_mutex_consistent_np() function will fail if:
ENOSYS The option _POSIX_THREAD_PRIO_INHERIT is not defined and the implementation does not support the function.
The pthread_mutex_consistent_np() function may fail if:
EINVAL The value specified by mutex is invalid, or the mutex does not have the appropriate attributes.
See attributes(5) for descriptions of the following attributes:
+-----------------------------+-----------------------------+
| ATTRIBUTE TYPE | ATTRIBUTE VALUE |
+-----------------------------+-----------------------------+
|MT-Level | MT-Safe |
+-----------------------------+-----------------------------+
pthread_mutex_lock(3C), pthread_mutexattr_getprotocol(3C), pthread_mutexattr_getrobust_np(3C), attributes(5), mutex(5), standards(5)
23 Mar 2005 pthread_mutex_consistent_np(3C)