I am working on getting LVM on my notebook. The easiest way may be to use the whole disk except for a small /boot partition which needs to be outside the LVM but with an initrd compiled with LVM support :
What LVM does is give more flexible partitions. Just think of them as logical volumes in an extended partition (the volume group). I think that is the best way to describe them. It is also possible to add extra space to them if needed, or even add partitions to make them bigger. That is how I see it. I hope I am right. If I am not I am sure someone will correct me.
I hope this helps.
Andy.
This User Gave Thanks to dragonnefyre For This Post:
Hi all,
yes this is a linux question :) but also a LVM question.
Some time ago, I saw an posting, LVM Version 1.X is abe to handle multiple physical pathes to a disk with using md devices. Is this right ?
Now I am planing to create a san and want use linux fileservers with LVM v1.X and most... (1 Reply)
I'm setting up a CentOS 5 server that will be connected to an HP EVA4000. My previous experience is with an HP VA7400 and HP-UX. In HP-UX I can add "alternate paths" to a volume group in order to have redundant paths to the SAN via dual fiber channel HBAs just by either adding them with... (3 Replies)
Not real Linux expert but here is the problem.
Shutdown this machine and then it would not reboot.
From everything I can tell it looks like the journal file in the logical volume is corrupted. I have tried everything I can think of to get the volume mounted.
Anybody have any ideas on how... (19 Replies)
Hi,
What do you means to create so OS Linux directories under LVM?
So, I've installed my machine :
df
Filesystem 1K-blocks Used Available Use% Mounted on
/dev/sda3 97943628 524316 92443984 1% /
udev 4023852 168 4023684 1% /dev... (1 Reply)
I've three partitions on /dev/sda: sda1, sda2 sda3. There is FREE space between sda2 and sda3 and sda3 ends on the last sector. sda2 and sda3 have the same number of sectors allocated and so are the exact same size.
/dev/sda2 is already part of the VG VolGroup. However, what puzzles me is that... (0 Replies)
My root file system is of type LVM. i wanna shrink it but unable to do so.
When i give the below command:
resize2fs /dev/mapper/VolGroup00-VolLog00 10000M
it messages that online shrink can't can't be done as the logical volume is mounted on /. i switched to single user mode by giving command:... (2 Replies)
Hi,
a little while ago, one of the GPT Partitioned hard disk had gone faulty in a Mirror RAID and is now successfully replaced.
here is how I did that.
1) created identical partition table on the new disk.
2) attached the mirrors using md commands.
The whole procedure is given... (5 Replies)
Hi,
I need a suggesstion i have 2 disk if i installed OS / root partition by making Lvm in one disk and data in other disk also with the lvm, means 2 different lvms.
Is making LVM partition for OS disk will the performacne will be good?
Can i make 2 different lvm one is for OS and other for... (1 Reply)
Discussion started by: Rahulne25
1 Replies
LEARN ABOUT REDHAT
vgimport
VGIMPORT(8) System Manager's Manual VGIMPORT(8)NAME
vgimport - make volume groups known to the system
SYNOPSIS
vgimport [-d|--debug] [-f|--force] [-h|--help] [-v|--verbose] VolumeGroupName PhysicalVolumePath [PhysicalVolumePath...]
DESCRIPTION
vgimport allows you to make a volume group known to the system which has previously been exported (see vgexport(8) ) on this or another
system.
OPTIONS
-d, --debug
Enables additional debugging output (if compiled with DEBUG).
-f, --force
Force import of volume group even though it is not flagged exported. This option allows the importing of volume groups from broken
systems.
-h, --help
Print a usage message on standard output and exit successfully.
-v, --verbose
Display verbose runtime information about vgimport's activities.
Examples
"vgimport myvg /dev/sd[b-h]5" tries to make new volume group "myvg" known to the system. The previously exported volume group (see vgex-
port(8) ) resides on disk partitions "/dev/sdb5" to "/dev/sdh5".
DIAGNOSTICS
vgimport returns an exit code of 0 for success and > 0 for error:
1 no volume group name on command line
2 invalid volume group name
3 no physical volume(s) on command line
4 volume group already exists
5 physical volume occurs mutiple times on command line
6 invalid physical volume name
7 error reading physical volume
8 physical volume is not exported
9 error reallocating memory
10 error allocating memory
11 no valid physical volumes found
12 physical volume belongs to a different exported volume group
13 wrong number of physical volumes
14 error reading VGDA from disk(s)
15 VGDA is inconsistent
16 invalid logical volume count
17 error getting a free volume group number
18 error writing VGDA to physical volumes
19 error creating VGDA in kernel
20 error inserting volume group into lvmtab
21 error doing backup of VGDA to disk
22 error storing VGDA in lvmtab
23 not enough free logical volume manager block specials available
95 driver/module not in kernel
96 invalid I/O protocol version
97 error locking logical volume manager
98 invalid lvmtab (run vgscan(8))
99 invalid command line
Example
"vgimport this_import /dev/sdk3 /dev/sdj4" tries to import a volume group contained on both partitions. The volume group this_import may
not already exit. You have to specify all physical volumes belonging to the exported volume group.
See alsolvm(8), lvcreate(8)AUTHOR
Heinz Mauelshagen <Linux-LVM@Sistina.com>
Heinz Mauelshagen LVM TOOLS VGIMPORT(8)