05-16-2013
Check status of a volume group
Hi huys,
Sorry for my bad english, i'm french
![Embarrassment Smilie](https://www.unix.com/images/smilies/redface.gif)
.
I've got a little question : is there a way to check status of a VG on aix 6.1 ? I want to know if a VG is locked or not...
I can do a "lsvg -Ll rootvg" for example, but if this VG is already locked, the process waits without gives me the hand...
Any idea ?
10 More Discussions You Might Find Interesting
1. UNIX for Advanced & Expert Users
Did anyone knows how to check size/usage of a Volume Group in AIX 4.3.3? (4 Replies)
Discussion started by: s_aamir
4 Replies
2. UNIX for Advanced & Expert Users
Hello,
I have logical volume group of 50GB, in which I have 2 logical volumes, LogVol01 and LogVol02, both are of 10GB.
If I extend LogVol01 further by 10GB, then it keeps the extended copy after logical volume 2. I want to know where it keeps this information
Regards
Himanshu (3 Replies)
Discussion started by: ghimanshu
3 Replies
3. AIX
Hi all,
I would like to ensure that a volume group has an effective quorum setting of 1 (or off). I know you can change the quorum setting using the chvg -Q command but want to know if the setting has been changed before the vg was varied on or a reboot.
In other words how can I ensure that... (3 Replies)
Discussion started by: backslash
3 Replies
4. AIX
Does anyone have any simple methods for moving a current logical volume from one volume group to another? I do not wish to move the data from one physical volume to another. Basically, I want to "relink" the logical volume to exist in a different volume group. Any ideas? (2 Replies)
Discussion started by: krisw
2 Replies
5. AIX
Hello,
I am a french computer technician, and i speak English just a little.
On Aix 5.3, I encounter a name conflict logical volume on two volume group.
The first volume lvnode01 is OK in rootvg and mounted. It is also consistent in the ODM
root # lsvg -l rootvg |grep lvnode01 ... (10 Replies)
Discussion started by: dantares
10 Replies
6. Red Hat
Hello,
How can I obtain a lists of disks with their size (anytype: SAN LUNs, internal disks, etc.) attached to the system and not being extended inside a volume group?
The purpose of this list is to be part of a function of a script that I'm doing in order to resize filesystems and in the... (6 Replies)
Discussion started by: asanchez
6 Replies
7. AIX
Hi,
I have a 2 node Cluster. Which is working in active/passive mode (i.e Node#1 is running and when it goes down the Node#2 takes over)
Now there's this requirement that we need a mount point say /test that should be available in active node #1 and when node #1 goes down and node#2 takes... (6 Replies)
Discussion started by: aixromeo
6 Replies
8. UNIX for Dummies Questions & Answers
Hi,
I am new to unix. I am working on Red Hat Linux and side by side on AIX also. After reading the concepts of Storage, I am now really confused regarding the terminologies
1)Physical Volume
2)Volume Group
3)Logical Volume
4)Physical Partition
Please help me to understand these concepts. (6 Replies)
Discussion started by: kashifsd17
6 Replies
9. UNIX for Dummies Questions & Answers
hi,
I want to create a volume group of 200 GB and then create different file systems on that.
please help me out. Its becomes confusing when the PP calculating PP.
I don't understand this concept. (2 Replies)
Discussion started by: kamaldev
2 Replies
10. Red Hat
Hello Guys,
I want to create a file system dedicated for an application installation. But there is no space in volume group to create a new logical volume. There is enough space in other logical volume which is being mounted on /var.
I know we can use that logical volume and create a virtual... (2 Replies)
Discussion started by: vamshigvk475
2 Replies
LEARN ABOUT OSF1
msem_lock
msem_lock(3) Library Functions Manual msem_lock(3)
NAME
msem_lock - Locks a semaphore
LIBRARY
Standard C Library (libc.a)
SYNOPSIS
#include <sys/mman.h>
int msem_lock ( msemaphore *sem, int condition );
PARAMETERS
Points to an msemaphore structure which specifies the semaphore to be locked. Determines whether the msem_lock() function waits for a cur-
rently locked semaphore to unlock.
DESCRIPTION
The msem_lock() function attempts to lock a binary semaphore.
If the semaphore is not currently locked, it is locked and the msem_lock() function returns successfully.
If the semaphore is currently locked, and the condition parameter is MSEM_IF_NOWAIT, then the msem_lock() function returns with an error.
If the semaphore is currently locked, and the condition parameter is 0 (zero), then msem_lock() will not return until either the calling
process is able to successfully lock the semaphore, or an error condition occurs.
All calls to msem_lock() and msem_unlock() by multiple processes sharing a common msemaphore structure behave as if the calls were serial-
ized.
If the msemaphore structure contains any value not resulting from a call to msem_init() followed by a (possibly empty) sequence of calls to
msem_lock() and msem_unlock(), the results are undefined. The address of an msemaphore structure may be significant. If the msemaphore
structure contains any value copied from an msemaphore structure at a different address, the result is undefined.
NOTES
Trial use
RETURN VALUES
On successful completion, the msem_lock() function returns 0 (zero). On error, the msem_lock() function returns -1 and sets errno to indi-
cate the error.
ERRORS
If the msem_lock() function fails, errno may be set to one of the following values: MSEM_IF_NOWAIT was specified and the semaphore was
already locked. The sem parameter points to an msemaphore structure which specifies a semaphore which has been removed, or the condition
parameter is invalid. The msem_lock() function was interrupted by a signal which was caught.
RELATED INFORMATION
Functions: msem_init(3), msem_remove(3), msem_unlock(3) delim off
msem_lock(3)