Create Logical Volume

Hello, I need to create some volumes in Solaris 9 on V240 with 2 HDD. The following is the table.
volume name -mount point-size-user-group-mode
fn_cache0-n/a-100m-fnsw-fnusr-664
How do I go about to archieve that? Thank you. I really appreciate help and guidence provided in the future.
Keith

What configuration file is this from? Are you asking for the commands to create a volume using Solaris Volume Manager or Veritas Volume Manager? Please provide more info.

Similar Messages

Creating Logical Volume during Oracle VM installation

Hello,
I am trying to install Oracle VM Server on a machine with 2 TB hard-disk. There are 2 disks each with 1 TB capacity.
During Oracle VM Server 2.2.2 installation, if you go with default partitions, layout looks like this
/dev/sda
   sda1          101M ext3        /boot
   sda2       952737M ocfs2       /OVS
   sda3         1027M swap
/dev/sdb
   sdb1         3074M ext3        /
   Free space 950792M Free SpaceIdeally I would like to give everything except what is needed by */ (root), /boot* and swap to */OVS*.
So from the layout above, I also want to give Free Space to */OVS*.
This excerpt talks about Logical Volume Creation during Oracle VM installation.
During the Oracle VM Server installation, press Alt+F2 to use the terminal, and run the lvm command. When you have finished creating the LVM configuration, press Alt+F1 to return to the Oracle VM Server installation.
But I couldn't figure out how to do this? Can anyone give me exact steps to achieve what I am trying to achieve.
regards, Yora

Hi again
It seems I downloaded by mistake the Oracle VM Server 3.0.1 Source for x86_64 (64 bit).
I should have downloaded the Oracle VM Server 3.0.1 for x86_64 (64 bit).
Now I can get started
Rudi

Unable to create logical volume snapshot

Hi All,
Pls note that the follwoing error is reported when a snapshot is being created in our Oracle Linux Server release 5.11 box:
[root@hawaii901 tmp]# lvcreate --size 500m --name snap /dev/ora_vg/vol02
Volume group name expected (no slash)
Run `lvcreate --help' for more information.
Any clue on this issue?
Thanks & Regards

LVM snapshot is a general purpose solution that was not designed with Oracle database in mind. It can be used, for example, to quickly create a snapshot prior to a system upgrade, then if you are satisfied with the result, you would delete the snaphot.
There is probably a common misconception. LVM snapshots, like all COW snapshosts that I'm aware off, allow to create a backup of a live filesystem while changes are written to the snapshot volume. Hence it's called "copy on write", or copy on change if you want. This is necessary for system integrity to make a complete backup of all data in a LVM volume at a certain point in time and to allow changes happening while the filesystem backup is taking place. A snapshot is no substitute for a disaster recovery backup in case you loose your storage media. A snapshot only takes seconds, and initially does not copy or backup any data, unless data changes. It is therefore important to delete the snapshot if no longer required, in order to prevent duplication of data and restore file system performance.
If snapshot or COW technololgy suits your purpose, you will actually want to look into BTRFS filesystem, which is more modern, employs the idea of subvolumes and is much more efficient that LVM.

Logical Volumes Not Creating w lvcreate? Install??

After following the arch raid guide i have gotten all tge way down to creating logical volumes and i get this
lvcreate -L 20G VolGroupArray -n lvroot
/dev/VolGroupArray/lvroot: not found: device not cleared
Aborting. Failed to wipe start of new LV.
device-mapper: remove ioctl on failed: Device or resource busy
here is vgdisplay
-- Volume group ---
VG Name VolGroupArray
System ID
Format lvm2
Metadata Areas 1
Metadata Sequence No 17
VG Access read/write
VG Status resizable
MAX LV 0
Cur LV 0
Open LV 0
Max PV 0
Cur PV 1
Act PV 1
VG Size 97.75 GiB
PE Size 4.00 MiB
Total PE 25024
Alloc PE / Size 0 / 0
Free PE / Size 25024 / 97.75 GiB
VG UUID rP0ooH-VdCy-fMZM-sB0g-90zi-Gv2o-gBZWC1
pls help i am now stuck

mattbarszcz wrote:So I went back to the live cd, I ran efibootmgr with no arguments, and sure enough there was only 1 entry for the Windows Boot Manager. It seems that efibootmgr commands don't seem to take effect.
Because of bugs in efibootmgr and/or EFI implementations, efibootmgr doesn't always work. Using bcfg from an EFI shell or bcdedit in Windows can be more effective on some systems. That said, if efibootmgr worked for you before, I'm not sure why it would stop working, or why an existing entry might disappear. (Some EFIs do delete entries that they detect are no longer valid. This shouldn't have happened with a whole-disk dd copy, but if you duplicated the partition table and then used dd to copy partitions, it might well have happened to you. I suppose it's conceivable that the firmware detected the change from one physical disk to another, too, and deleted the original entry because of that change.)
I referenced the rEFInd page here: http://www.rodsbooks.com/refind/installing.html#windows and followed the procedure to install an entry for rEFInd from Windows. I was able to add an entry no problem through windows.
Does anyone have any suggestions as to why this doesn't work? Nothing has changed about the system other than the disk.
It's unclear from your post whether the entry you created in Windows now works. If it does, then don't sweat it; just keep using that entry, and if you need to make changes and efibootmgr doesn't work in the future, plan to use either Windows or the bcfg command from an EFI version 2 shell.

[SOLVED]using dd to make image backup of logical volume?

I recently got my Ocz Revodrive working under Archlinux by creating logical volumes on it which worked out great, i also got openbox configured to my liking but i want to make an image back up of my Revodrives logical volumes into image files to restore for later use. I was reading the disk cloning wiki about the dd command and just wanted to double check that the dd command below would work ok?
Once i boot into the Arch live usb, and run the following commands it should create an image file on the hard drive mounted under /mnt/backupdata ? Sorry for the straight forward question, i just want to make sure i have the right command before i back up data i dont have a copy of.
dd if=/dev/mapper/VolGroupArray-lvroot of=/mnt/backupdata/test.img bs=16m
dd if=/dev/mapper/VolGroupArray-lvhome of=/mnt/backupdata/test.img bs=16m
Also anyone have any feedback on what blocksize to use for backing up to a standard hard drive, is 16m okay?
Last edited by itzmeluigi (2013-08-05 06:01:54)

Oops heh, i would usually rename it to test1.img and test2.img, i was using it as an example. Once i create the images, would the commands below be the proper way to restore them?
dd if=/mnt/backupdata/test1.img of=/dev/mapper/VolGroupArray-lvroot bs=16m
dd if=/mnt/backupdata/test2.img of=/dev/mapper/VolGroupArray-lvhome bs=16m
Thanks
Edit: All the commands ended up working perfectly i had to change the lower case m to bs=16M. Once i did that the image files were created and worked just fine
Last edited by itzmeluigi (2013-08-05 06:01:30)

Can't delete a logical volume group created from a blank disk image

Hi all,
I'm a recent convert from Windows, so do bear with me while I grapple with all the new terminology.
Basically, here's the problem: I've been trying to create an encrypted drive and have been at it for a few hours now. I ended up with two 'logical volume groups' created from blank disk images, neither of which are password-protected, and one of which I quite stupidly named "hidden folder" and can't rename now. Anyways, I decided to throw it all away and start right from scratch, but now disk utility won't let me delete these two logical volume groups despite me dismounting both devices, trying to trash the containing folder, etc. Some searching about online has gotten me into the belief that there should be an 'erase' tab in the disk utility window which is not showing up when I click on those drives (however, the erase tab does appear when I click on the indented partitions on each drive). Here's a screenshot to give you guys an idea:
-Here's the disk utility window. The two drives I'm trying to get rid of are "Hidden Folder" and "HD2"
-Here's what I suppose would be called the 'containing folder' in which both drives reside
-And finally my setup, just in case it's relevant
Oh and btw this would be my first post here! How exciting
Thanks in advance,
Arthur

nidra wrote:
When I right click on it these are the choices: Open; Move to Trash; Get Info; Compress...; Burn ... to disc; Duplicate; Make Alias; Copy ...; Clean Up Selection; Show view options; Label; Folder Actions Setup.
That is as it should be. If you select "Move to Trash" does it move the folders to the trash? If so, do the following from my previous post:
tjk wrote:
1. Open Terminal (in Applications, Utilities).
2. Copy and paste the following command into the Terminal window (or type it exactly as follows):
sudo rm -rf ~/.Trash/*
3. Press Return.
4. Type in your password when asked (note: you will not see anything being entered as you type your password).
5. Hit Return.
6. Wait until the process finishes/the Terminal prompt returns.
7. Quit Terminal.
I wonder if I need to do some changes to the rights about doing this action "move to trash"?
Run Repair Permissions in Disk Utility.
this is making me very uncomfortable, I know myself to solve any problems I tackle/___sbsstatic___/migration-images/migration-img-not-avail.png Something so simple as this is making me crazy
I don't know if it would make me any crazier than I am, but I sure wouldn't want a stray folder just hanging around on my desktop either.

Volume encrypt and erase failed; unable to delete core storage logical volume

I was attempting to slowly migrate [MI-***] from early 2013 MBPRO to New iMac 5K w/Ceiling Level components.
Kept going through LONG process and then told me it couldn't create [MBPRO HD Home Username] "Jim" on volume or whatever. NO FileVault enabling/ still skittish from White iMac Encrypting Nightmare days... I don't even know -- I guess it's encrypted on Airport, but not on MBPRO.
Moved over Applications from outside User account fine; anything inside any User account NOT FINE.
Hooked up Thunderbolt cable between two macs and restarted MBPRO in T mode... displaying the lightning BOLT on screen that moves around to reduce Burn-in.
Was able to go onto desktop and use windows to drag n drop 190G of movies over to iMac... wondering how I was going to get all right settings over form FCP...
Bottom Line: I only have 16G left on MBPRO and need to MOVE video editing to be exclusive on 3T Fusion on Maxed out iMac 5K.
> Have concluded through whole process that I just want to clone the MBPRO and then delete most of the Larger Videos from MBPRO to recover some of my 760G SSD back.
So, I grabbed my 2T Airport Extreme and Hooked up the Cat5 LAN port to Cat5 input on back of NEW iMac; Now my MBPRO doesn't have to be locked up for days, because i can use TimeMachine backup to restore or clone the two macs... i hope.
Went into recovery mode and selected sub-Macintosh HD and attempted to erase; Result time after time after time: "Volume Encrypt and Erase failed." Reason: "Unable to delete the Core Storage logical volume." It dismounts it and I have to restart computer to get it back on. Funny thing is I don't have to use R anymore... which by the way, Command+R appears to be same as just plain old R when restarting... why is that?
This has become a "since Christmas" runaround session for me and I am sick of it.
Please help. I would've called Apple Care [and I did last night while driving... just to get advice on direction. I'm usually a pretty savvy PowerUser but this is driving me crazy.] but have to get things done for a meeting tomorrow. Can work on it after hours if someone can advise today on this post.
Thx,
Jim

I have taken some screenshots of the error I get and the state of my HDD in Disk Utility. I did have a weird thing happen after trying to repair using single user mode, where I reopened disk utility and the partitions were NOT greyed out and displayed the correct info concerning space available etc, although after verifying it then reverted back to greyed out with no info.

Logical Volume Manager

I am planning on installing Arch on a laptop soon. I have played with it in VirtualBox on a separate computer, and I am going to hope that it works with my touchpad / wireless mouse.
I might butcher some jargon in this, but this is how I think LVMs work, and I would like to make sure.
I am going to make partitions for boot, swap, /, and /home.
I know boot only needs to be around 100MB, swap is twice the RAM -- and I saw in another thread, / around 10-15GB -- and /home is the rest.
However, I read about installing on an LVM and it is easy to re-size partitions if needed.
I only have 1 HD, and I'm mostly doing this because while I do have room to have too much space on /, if I end up only using around 4GB, I would like to have that 11GB on my /home for music or videos.
So I think that means I would have something like this:
sda1: boot, around 100MB.
sda2: LVM, which contains swap, /, and /home.
pvcreate /dev/sda2 creates the physical volume on the LVM, allowing me to partition it.
After that, this is where I am confused.
The Arch Wiki says:
Create Volume group(s)
Next step is to create a volume group on this physical volumes. First you need to create a volume group on one of the new partitions and then add to it all other physical volumes you want to have in it:
# vgcreate VolGroup00 /dev/sda2
# vgextend VolGroup00 /dev/sdb1
Also you can use any other name you like instead of VolGroup00 for a volume group when creating it. You can track how your volume group grows with:
Can I skip this since I have only 1 HD? I guess that /dev/sdb1 is the LVM from the other harddrive?
I suppose I would have to do vgcreate VolGroup00 /dev/sda2 just to create the volume goup, though. Is this correct?
After this step, I am pretty much lost. Here's what the wiki says, and how I am interpreting it...
# lvcreate -L 10G VolGroup00 -n lvolhome
This will create a logical volume that you can access later with /dev/mapper/Volgroup00-lvolhome or /dev/VolGroup00/lvolhome. Same as with the volume groups you can use any name you want for your logical volume when creating it.
So later, I would turn this into my home partition during the Arch installation? I would create a lvolswap, and a lvolroot?
Then, during the installation process, I would format them to ext3, and mount them as /home, /, and then select lvolswap as my swap partition?
That's about it for now, I guess.
Last edited by COMMUNISTCHINA (2008-08-15 21:53:41)

COMMUNISTCHINA wrote:
Berticus wrote:
COMMUNISTCHINA wrote:I dunno. I tried using LVM on a virtualbox and I keep getting a kernel panic. I followed the Wiki.
If I put GRUB on /boot, it doesn't work, but I got it to work if I installed it on the / LV.
odd, to my knowledge grub can't be on an LVM. why not install grub on MBR?
I actually figured this out maybe an hour ago.
I changed my GRUB configuration file, but since it's in a virtualbox, out of habit I type arch root=/dev/sda3 on startup, but I needed to type root=/dev/VG00/lvolroot. I had grub on /boot (not on the LVM), but when I was trying to boot, I told it to go to the wrong place for root. I could probably unmount the .iso for the vbox, but whatever.
I will read a little more about RAID.
If I end up figuring out how to do it, would I need my external hooked up to it all the time? I have tote the laptop around, and I wouldn't want the external mucking up the portability.
I wasn't aware you were on a laptop. In that case, a file server would do you best. But cheapest solution would be just to stick with an external hard drive and not RAID.

Installing OS X Yosemite has changed my Macintosh HD type to Logical Volume Group

I have just installed OS X 10.10 Yosemite on my late 2013 MacBook Pro with Retina Display,
The installation has worked perfectly and my computer is now running fine. However after opening disk utility I have noticed where previously my HD would be named "Apple SSD...." and the partition underneath would be named Macintosh HD, both are now the same. Also, previously the HD was GUID type and now they have changed to Logical Volume Group and Logical Partition.
I installed the software by creating a bootable memory stick with OS X 10.10 and completed a clean install by completely erasing the HD and then installing the new software. After the HD had been erased, Disk Utility still showed the HD as "Apple SSD...." with the partition "Macintosh HD" below and with Type: GUID. It wasn't until after the installation was complete and I had set up the computer and then gone back into Disk Utility when I released it had changed to both labels being "Macintosh HD" and the format type being Logical Volume Group and Logical Partition.
I have no clue if this is normal and was a planned changed (i.e the software was designed to change it) or if my installation has gone horribly wrong. Can the HD format type be changed back or does Yosemite have to run on Logical Partition and Logical Volume Group formatted HD's.
Any help would be appreciated as I'm not an expert and I have tried googling for hours and can't find anything helpful/useful or that will work.

It's a designed change during the Yosemite install process. John Siracusa's excellent review of Yosemite over at Ars Technica provides some commentary on the change, specifically this page: http://arstechnica.com/apple/2014/10/os-x-10-10/2/

Can I Install Multiple Partitions in a Logical Volume Group

I have a 3 TB Fusion Drive which is not partitioned and type is Logical Volume Group. In Disk Utility I have two tabs First Aid and Partition. In partition I can only divide it into two partitions is there anyway to change this so I can create more partitions?

(Instructions for XP Pro and Acrobat 8.0)
Open the printers folder and click on Add a printer.
Click Next on the Welcome screen
Select 'Local Printer attached to this computer', uncheck Automatically detect and install my Plug and Play printer, click Next
Click on Create a new port, select 'Adobe PDF Port' from the list, click Next
Select the folder you want the PDF stored in, click OK
On the Install Printer Software screen click on Have Disk
Click on the Browse button and browse to 'Program Files\Adobe\Acrobat 8.0\Acrobat\xtras\AdobePDF' (May be different for your setup)
Select the AdobePDF.inf (English version) and click OK
Select the Adobe PDF Convertor (there may be several listed, I always choose the top one) and click Next
If the Use Existing Driver dialog is displayed select 'Keep existing driver' click Next
Name the Printer i.e. Adobe PDF 1, click Next
Set the sharing options, print a test page if you wish and finish.
Now when you print to this printer from within an application it will create the PDF in the specified folder
You can repeat this process for a number of outputs.
Hope this helps

Unix layout question single vs. multiple logical volumes

Hello friends,
I have a question which I have seen various points of view. I'm hoping you might be able to give me a better insight so I can either confirm my own sanity, or accept a new paradigm shift in laying out the file system for best performance.
Here are the givens:
Unix systems (AIX, HP-UX, Solaris, and/or Linux).
Hardware RAID system on large SAN (in this case, RAID-05 striped over more than 100 physical disks).
(We are using AIX 6.1 with CIO turned on for the database files).
Each Physical Volume is literally striped over at least physical 100 disks (spindles).
Each Logical Volume is also striped over at least 100 spindles (all the same spindles for each lvol).
Oracle software binaries are on their own separate physical volume.
Oracle backups, exports, flash-back-query, etc., are on their own separate physical volume.
Oracle database files, including all tablespaces, redo logs, undo ts, temp ts, and control files are in their own separate physical volume (that is made up of logical volumes that are each striped over at least 100 physical disks (spindles).
The question is if it makes any sense (and WHY) to break up the physical volume that is used for the Oracle database files themselves, into multiple logical volumes? At what point does it make sense to create individual logical volumes for each datafile, or type, or put them all in a single logical volume?
Does this do anything at all for performance? If the volumes are logical, then what difference would it to put them into individual logical volumes that are striped across the same one-hundred (+) disks?
Basically ALL database files are in a single physical volume (LUN), but does it help (and WHY) to break up the physical volume into several logical volumes for placing each of the individual data files (e.g., separating system ts, from sysaux, from temp, from undo, from data, from indexes, etc.) if the physical volume is created on a RAID-5 (or RAID-10) disk array on a SAN that literally spans across hundreds of high-speed disks?
If this does makes sense, why?
From a physical standpoint, there are only 4 hardware paths for each LUN, so what difference does it make to create multiple 'logical' volumes for each datafile, or for separating types of data files?
From an I/O standpoint, the multi-threading of the operating system should only be able to use the number of pathways that are capable based on the various operating system options (e.g., multicore CPUs using SMT (simultaneous multipath threading). But I believe they are still based on physical paths, not based on logical volumes.
I look forward to hearing back from you.
Thanks.
ji li

Thanks for your reply damorgan.
We have dual HBAs in our servers as standard equipment, along with dual controllers.
I totally agree with the idea of getting rid of RAID-5, but that is not my choice.
We have a very large (massive) data center and the decision to use RAID-5 was at the discretion of our unix team some time ago. Their idea is one-size-fits-all. When I questioned it, I was balked at. After all, what do I know? I've only been a sys admin for 10 years (but on HP-UX and Solaris, not on AIX), and I've only been an Oracle DBA for nearly 20 years.
For whatever it is worth, they also mirror their RAID-5, so in essence, it is a RAID 5-1-0 (RAID-50).
Anyway, as for the hardware paths, from my understanding, there are only 4 physical hardware paths going from the servers to the switches, to the SAN and back. Their claim (the unix team's) is that by using multiple logical volumes within a single physical volume, that it increases the number of 'threads' to pull data from the stripe. This is the part I don't understand and may be specific to AIX.
So if each logical volume is a stripe within a physical volume, and each physical volume is striped across more than one hundred disks, I still don't understand how multiple logical volumes can increase I/O through-put. From my understanding, if we only have four paths, and there are 100+ spindles, even if it did increase I/O somehow by the way AIX uses multipathing (SMT) with its CPUs, how can it have any affect on the I/O. And if it did, it would still have to be negligible.
Two years ago, I've personally set up three LUNs on a pair of Sun V480s (RAC'd) connected to a Sun Storage 3510 SAN. One LUN for Oracle binaries, one for database datafiles, and one for backups and archivelogs), and then put all my datafiles in a single logical volume on one LUN, and had fantastic performance for a very intense database that literally had 12,000 to 16,000 simultaneous active* connections using Webshere connection pools. While that was a Sun system, and now I'm dealing with an AIX P6 570 system, I can't imagine the concepts being that much different, especially when the servers are basically comparable.
Any comments or feedback appreciated.
ji li
Edited by: ji li on Jan 28, 2013 7:51 AM

RAID on LVM logical volumes

Hey,
i've got a 1T and a 500G hard drive in my workstation. The 500G drive is my media disk. I initialized a software RAID-1 with one missing drive on a 500G logical volume on the 1T disk. After formatting and copying all the data from the media disk over to the new raid partition, I added the old 500G partition to the RAID.
After rebooting my machine, the RAID was in inactive state and hence the filesystem could not be mounted.
I found out, that in /etc/rc.sysinit the search for software RAID arrays is performed before the search for LVM volume groups. I started switching the RAID and LVM sections but after reboot nothing changed. I presume it's caused by the lv devices missing in /proc/partitions, which is used by md to scan for raid members by default.
I decided to add some lines to /etc/rc.local (also my RAID device is /dev/md127 Oo):
mdadm --stop /dev/md127
mdadm --assemble /dev/md127 /dev/vg00/raid-data /dev/sdb1
mount /mnt/raid
It works now, but it is not a clean solution.
How is it supposed to do RAID on top of LVM logical volumes in Arch Linux? Are there any alternative ideas of solutions to this problem (sure there are)?
Thanks in advance.

delcypher wrote:
Hi I've been looking into backing up one of my LVM logical volumes and I came across this (http://www.novell.com/coolsolutions/appnote/19386.html) article.
I'm a little confused by it as it states that "Nice work, your logical volume is now fault tolerant!".
Are you sure that's the article? I can't find anything on that page about "nice work" or "fault tolerant"...?
delcypher wrote:My concern is that because my volumegroup spans across two drives if anyone of them fails I will loose all may data.
Correct.
delcypher wrote:Is there any setup I can do by which I can have a perfect mirror of my volumegroup so that if one of my drives fail I still have a perfectly function volumegroup.
Use 2 disks to create a RAID-1 array, then use that as your PV.
sda1 + sdb1 = md0 => pv
delcypher wrote:I understand linux supports software raid but would I need two drives identically sized (1TB) or can I just have one drive (i.e. 2TB) that is a mirror of my volumegroup?
You can use 2 partitions on the same disk to create a RAID array, but that defeats the whole purpose of RAID.
It sounds like you're merging the meanings of 'redundant' and 'backup' -- they are distinct things, so you need to decide if you want redundancy or backup. Or both ideally.

How to delete existing "Logical volume" from V880

i have a V880 server. it have some Logical volume previously. but i want to delete that old Logical volume and then want to create new LV's. so how can i delete the old LV's.

If you're talking about SVM, then 'metaclear' will destroy a metadevice object that is not in use.
Darren

Not able to create a Volume Group in the oracle VM server installation

Hi,
I am installing Oracle VM server. In the installtion ( Partition time ), i click on create custom layout and i want to create a / partition as a logical volumn under volume group. But there is no option to create a Volume group actually. So can anybody help how to create a volume group actually and how to create a logical volume under volume group.

user10274248 wrote:
So can anybody help how to create a volume group actually and how to create a logical volume under volume group.LVM is not recommended in Dom0, which is why support for LVM has been removed from the installer. LVM is not cluster aware and does not support write barriers, both of which are important for a filesystem that is used for storing file-backed disk images.

LVM2 - installer "see" already existing logical volumes [SOLVED]

I've been messing about with LVM for about a week now and ran into a snag with the installer.
Essentially if, for whatever reason, I make my logical volumes, then reboot and start the installer it won't "see" my L.Vols at all. I did the
modprobe dm_mod
before starting and after starting the installer. The result is still the same either way. I ended up removing the L.Vols and re-creating them, then running the installer again. It seems to be the only way I can get the setup scripts to "find" the Logical Volumes properly if the Physical Extent/Volume Group/Logical Volumes pre-existed before invoking /arch/setup.
I searched the installation forum but the closest thing I found was this from a year ago: http://bbs.archlinux.org/viewtopic.php?id=48483. I'm a bit baffled as to how I can get the installation routine to recognise the volumes exist so I don't need re-create things every time I want to do another install. Any advice is appreciated.
*goes to search elsewhere*
MS
Last edited by MoonSwan (2009-04-06 23:11:26)

I think once you've modprobe dm_mod, u should be able to do a bunch of commands to activate existing volume groups and logical volumes. I'm running an lvm setup and it took me ages to suss it all out and get up and running.
You can definitely do an lvscan command which should look for logical volumes and list them for you. I think you can activate them through there too. Does doing any of the following give you anything once you've done the modprobe?
pvdisplay
vgdisplay
lvdisplay
Also
ls -al /dev/mapper (I think) should lisy the devices for lvm tht already exist. Sorry can't be more accurate for you at the mo, am not in front of my linux box. :-(

Create Logical Volume

Similar Messages

Maybe you are looking for