08-27-2009
Thanks for your reply.
I'm in confusion. I have LVM's like
/dev/mapper/VolGroup00-LogVol00 -10gb /
/dev/mapper/VolGroup00-LogVol01 -2gb /tmp
/dev/mapper/VolGroup00-LogVol03- 500mb /opt
/dev/mapper/VolGroup00-LogVol04 - 10gb /var
so if i remove /dev/mapper/VolGroup00-LogVol01, i should see 2gb free space right? how can I check that?
and also I need to increase /dev/mapper/VolGroup00-LogVol03 to 2gb from 500mb. how can i do this?
Thanks
9 More Discussions You Might Find Interesting
1. 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
2. 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
3. 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
4. HP-UX
Hi,
Someone please help me with how i can unmount and remove all the files systems from a cluster. This is being shared by two servers that are active_standby. (3 Replies)
Discussion started by: joeli
3 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. 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. 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
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
DM(4) BSD Kernel Interfaces Manual DM(4)
NAME
dm -- Device-mapper disk driver
SYNOPSIS
pseudo-device dm
DESCRIPTION
The dm driver provides the capability of creating one or more virtual disks based on the target mapping.
This document assumes that you're familiar with how to generate kernels, how to properly configure disks and pseudo-devices in a kernel con-
figuration file, and how to partition disks. This driver is used by the Linux lvm2tools to create and manage lvm in NetBSD.
Currently, the linear, zero, and error targets are implemented. Each component partition should be offset at least 2 sectors from the begin-
ning of the component disk. This avoids potential conflicts between the component disk's disklabel and dm's disklabel. In i386 it is offset
by 65 sectors, where 63 sectors are the initial boot sectors and 2 sectors are used for the disklabel which is set to be read-only.
In order to compile in support for dm, you must add a line similar to the following to your kernel configuration file:
pseudo-device dm #device-mapper disk device
dm may create linear mapped devices, zero, and error block devices. Zero and error block devices are used mostly for testing. Linear
devices are used to create virtual disks with linearly mapped virtual blocks to blocks on real disk. dm Device-mapper devices are controlled
through the /dev/mapper/control device. For controlling this device ioctl(2) calls are used. For the implementation of the communication
channel, the proplib(3) library is used. The protocol channel is defined as a proplib dictionary with needed values. For more details, look
at sys/dev/dm/netbsd-dm.h. Before any device can be used, every device-mapper disk device must be initialized. For initialization one line
must be passed to the kernel driver in the form of a proplib dictionary. Every device can have more than one table active. An example for
such a line is:
0 10240 linear /dev/wd1a 384
dm The first parameter is the start sector for the table defined with this line, the second is the length in sectors which is described with
this table. The third parameter is the target name. All other parts of this line depend on the chosen target. dm For the linear target,
there are two additional parameters: The first parameter describes the disk device to which the device-mapper disk is mapped. The second
parameter is the offset on this disk from the start of the disk/partition.
SEE ALSO
config(1), proplib(3), MAKEDEV(8), dmsetup(8), fsck(8), lvm(8), mount(8), newfs(8)
HISTORY
The device-mapper disk driver first appeared in NetBSD 6.0.
AUTHORS
Adam Hamsik <haad@NetBSD.org> implemented the device-mapper driver for NetBSD.
Brett Lymn <blymn@NetBSD.org>,
Reinoud Zandijk <reinoud@NetBSD.org>, and
Bill Stouder-Studenmund <wrstuden@NetBSD.org> provided guidance and answered questions about the NetBSD implementation.
BUGS
This driver is still work-in-progress--there can be bugs.
BSD
August 30, 2008 BSD