10-22-2007
The problem may be that the hdisk (which seems to come from some storage subsystem) is already in use on another system. The system will discover the PVID and the VG-information only after establishing access to the disk, which isn't possible as long as it is used by another system concurrently.
bakunin
10 More Discussions You Might Find Interesting
1. AIX
Hi All,
There is AIX server which has 2 internal disks running the OS and 8 external disks on a RAID array with RAID 5. My question - is there a way to check which are the logical volumes and file system configured on this RAID array (2 Replies)
Discussion started by: rramanuj
2 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
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
4. AIX
Hi!
Can anyone help me on how I can do a basic check on the Unix filesystems / physical volumes and logical volumes?
What items should I check, like where do I look at in smit? Or are there commands that I should execute?
I need to do this as I was informed by IBM that there seems to be... (1 Reply)
Discussion started by: chipahoys
1 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. Solaris
What are the comman line instructions need to be used to know if a Logical Volume Manager is installed on solaris Box, What is its name, version, driver version, library version. (1 Reply)
Discussion started by: epriya2003
1 Replies
7. HP-UX
Hi to all,
I am brand new to HP-UX but am quite familiar with Linux systems (Red Hat, Ubuntu etc..)
I've just taken over a new HP-UX box and trying to work out how to create a logical volume.
As well as creating the volume, which I am sure is very easy I need to create a special character... (6 Replies)
Discussion started by: jamie2teach
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. AIX
Hello everyone,
I just read that while creating a logical volume(LV) we can choose the region of the physical volume (PV) in which the LV should be created.
When I say region I mean: outer edge - outer middle - center - inner middle and inner edge.
Can anyone help me understand the utility... (11 Replies)
Discussion started by: adilyos
11 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 HPUX
diskowner
diskowner(1M) diskowner(1M)
NAME
diskowner - retrieve the owner of a storage device
SYNOPSIS
path
DESCRIPTION
The command is used to retrieve the subsystem, if any, which is using the specified path. The command is intended to help prevent users
from overwriting storage that is already in use. The command will print out the owner of the path, or if no owner was found. A storage
device is considered owned by a subsystem if it has been formatted by that subsystem. For example, if a disk contains a VxFS filesystem,
but is not mounted or in use, it is still considered owned by the VxFS subsystem.
If the path specified is invalid or inaccessible, an error message will be printed.
Options and Arguments
The command recognizes the following options and arguments:
path The path name to the storage device. The path may be a symbolic link, as long as it points to a storage device, such as a file,
disk, or logical volume.
List all the owners of the specified path, seperated by commas
Produce a compact output that is easily parsed by other scripts and
programs. When used with option, displays all the owners seperated by dots This format is described in the section below.
Output from diskowner
displays the following possible output:
owner The owner of the given path. owner can be one of the following:
The path is not owned by any known subsystem.
The path is part of an LVM volume group.
The path is part of a VxVM volume group.
The path has a VxFS filesystem on it.
The path has a HFS filesystem on it.
The path is being used as a swap device.
The path is being used as a dump device.
The path is part of an Oracle database.
The path has EFI partitions on it.
message An error message displayed when the given path is invalid or inaccessible.
Compact Listing
The option generates a compact, colon delimited listing that is easy to parse. The output format is:
and so forth.
The option, when used with the option, produces this output format:
and so forth.
The current command prints out the keys and values listed below. In the future, new keys and/or values may be added to the output.
or
or
where
path is the pathname passed as argument
owner is the owner of the given path
message is an error message when given path is invalid or inaccessible.
n is number of owners of the given path
EXTERNAL INFLUENCES
Environment Variables
determines the language in which messages are displayed.
If is not specified or is null, it defaults to "C" (see lang(5)).
If any internationalization variable contains an invalid setting, all internationalization variables default to "C" (see environ(5)).
RETURN VALUE
Upon completion, returns one of the following values:
The path is not owned (the owner is
The path is already owned by a subsystem.
The path does not exist.
Invalid options or library version incompatible.
The path cannot be opened due to an I/O error.
The path cannot be opened due to insufficient permissions.
The path format is invalid.
EXAMPLES
Display the owner of a disk path:
Display the owner of a logical volume in compact output:
Display all the owners of a disk path:
Display all the owners of a logical volume in compact output:
SEE ALSO
crashconf(1M), df(1M), swapinfo(1M), vgdisplay(1M), vxvmboot(1M), vxassist(1M), fstab(4).
diskowner(1M)