01-08-2004
Yes, the hdisk3 is a partition of the Raid array.. (raid 1)
The error message is something like:
The LVM returned an unknown code (3).
Or when I try to remove the vg, the message is: Failed to execute the programm ' '
and when I try to do all the other commands, usually I get : The Volume Group must varied on first.. Use the varyonvg command..
10 More Discussions You Might Find Interesting
1. AIX
Looking for help in understanding volume groups.
On the internal disks is it possible to have other volume groups other then root vg? If so would the other vg be captured in the mksysb?
Any documentation links that you can point me to on volume groups and such woudl be welcomed.
Thanks (1 Reply)
Discussion started by: cogsworth12000
1 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
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
5. 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
6. 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
7. Red Hat
Our SAN administrator decided to unpresent then destroy LUN's we were actively using as a volume group (all PV's in said volume group). Now every time I do a pvscan or whatever it complains about I/O errors trying to access those PV's. How do I get it to forget the VG existed completely? vgreduce... (7 Replies)
Discussion started by: thmnetwork
7 Replies
8. 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
9. 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
10. AIX
I want to remove hdisk1 from volume group diskpool_4 and migrate PV from hdisk1 to hdisk2 , but facing problems, so what is the quickest way to migratepv and remove hdisk1 --
# lspv | grep diskpool_4
hdisk1 00c7780e2e21ec86 diskpool_4 active
hdisk2 ... (2 Replies)
Discussion started by: filosophizer
2 Replies
LEARN ABOUT CENTOS
blkdeactivate
BLKDEACTIVATE(8) BLKDEACTIVATE(8)
NAME
blkdeactivate - utility to deactivate block devices
SYNOPSIS
blkdeactivate [options] [device...]
DESCRIPTION
blkdeactivate utility deactivates block devices. If a device is mounted, the utility can unmount it automatically before trying to deacti-
vate. The utility currently supports device-mapper devices, including LVM volumes. LVM volumes are handled directly using the lvm command.
Other device-mapper based devices are handled using the dmsetup command.
OPTIONS
-e, --errors
Show errors reported from tools called by blkdeactivate. Without this option, any error messages from these external tools are sup-
pressed and the blkdeactivate itself provides only a summary message about device being skipped or not.
-h, --help
Display the help text.
-u, --umount
Unmount a mounted device before trying to deactivate it. Without this option used, a device that is mounted is not deactivated.
-v, --verbose
Run in verbose mode.
-d, --dmoption dm_options
Comma separated list of device-mapper specific options.
-l, --lvmoption lvm_options
Comma separated list of LVM specific options.
DM_OPTIONS
retry Retry removal several times in case of failure.
force Force device removal. See dmsetup(8) for more information.
LVM_OPTIONS
retry Retry removal several times in case of failure.
wholevg
Deactivate the whole LVM Volume Group when processing a Logical Volume. Deactivating Volume Group as a whole takes less time than
deactivating each Logical Volume separately.
EXAMPLES
Deactivate all supported block devices found in the system. If a device is mounted, skip its deactivation.
blkdeactivate
Deactivate all supported block devices found in the system. If a device is mounted, unmount it first if possible.
blkdeactivate -u
Deactivate supplied device together with all its holders. If any of the devices processed is mounted, unmount it first if possible.
blkdeactivate -u /dev/vg/lvol0
Deactivate all supported block devices found in the system. Retry deactivation of device-mapper devices in case the deactivation fails.
Deactivate the whole Volume Group at once when processing an LVM Logical Volume.
blkdeactivate -u -d retry -l wholevg
Deactivate all supported block devices found in the system. Retry deactivation of device-mapper devices in case the deactivation fails and
force removal.
blkdeactivate -d force,retry
SEE ALSO
lsblk(8) umount(8) dmsetup(8) lvm(8)
Red Hat, Inc LVM TOOLS 2.02.105(2)-RHEL7 (2014-03-26) BLKDEACTIVATE(8)