Solaris9 Logical Volume Manager

Dear All,
I want to know more about Logical Volume Manager in Solaris9.
I know that it makes logical volumes from one disk or more?
are these Logical Volumes like a disk can be used for striping datafiles into them if I use RAID 5 controller in Oracle Database?

no replies???????

Similar Messages

Unable to find Logical Volume manager in OEL6

Hi Guru's,
I am new to Linux.
I have installed OEL6 in my windows box with Virtual Box.
After logging in
i don't see
the Logical Volume manager
and Network option under Administration menu too.
I tried to install lvm-1.0.8-14.x86_64.rpm (downloaded from redhat) but no luck.
Please help me to fix this.
Thank you
chandra

I remember the Red Hat 6.0 release notes outlining that Samba and LVM configuration GUI were removed without a replacement. Same goes for the system-network-config tool. More recent versions of the release notes at http://docs.redhat.com/docs/en-US/Red_Hat_Enterprise_Linux/6/html/6.0_Release_Notes/storage.html outline that system-config-lvm is in the process of transitioning to a more maintainable tool named gnome-disk-utility.
You did not specify which version of Oracle Linux you installed. I suggest you refer to the release notes. A text based version of "system-config-network" should still be installed, which you can open from the command line.
Regarding LVM gui you should setup the system software repository following the instructions at http://public-yum.oracle.com. You can then use yum to install the system-config-lvm package.

Linux LVM (Logical Volume Manager) for CentOS on Azure?

Hi. I am trying out Azure and installed a OpenLogic CentOS 6 virtual machine. I note that it is not running LVM (Logical Volume Manager) by default. I would like to ask if it is possible to:
1. have CentOS Linux installed with LVM by default when creating a Linux virtual machine on Azure
2. switch to LVM after adding a new disk
On the other hand, is it a good idea to use LVM at all? Will it affect performance, features on Azure?
Thanks.

Hi,
Based on my experience, you can add disk to an Azure VM. You can install the Logical Volume Manager to manage the disks attached to the VM. In addition, there is no Linux VM with LVM installed by default. If you want to have this, please submit your requirement
in Azure feedback:
http://feedback.azure.com/forums/34192--general-feedback
In addition, since you can have only one OS system disk for an Azure VM, this limitation may make multi-disk logical volume manager setups unworkable.
Best regards,
Susie
Please remember to mark the replies as answers if they help and unmark them if they provide no help. If you have feedback for TechNet Subscriber Support, contact [email protected]

Finding whole mapping from database file - filesystems - logical volume manager - logical partitions

Hello,
Trying to make reverse engeneering of database files and their physical carriers on logical partitions ( fdisk ).
And not able to make whole path from filesystem down to partitions with intermediate logical volumes.
1. select from dba_data_files ...
2. df -k
to get the listing of filesystems
3. vgdisplay
4. lvdisplay
5. cat /proc/partitions
6. fdisk /dev/sda -l
   fdisk /dev/sdb -l
Problem I have is that not able to determine which partitions are consisten in logical volumes. And then which logical volumens are consisted in filesystem.
Thank you for hint or direction.

Hello Wadhah,
Before start the discussion let me explain I am newcommer to Oracle Linux. My genetic with dba experience of Oracle is from IBM UNIX ( AIX 6.1 ) and Oracle 11gr2.
First task is to get the complete picture of one database on Oracle Linux for future maintenance tasks and make database more flexible and
preparing for more intense work:
-adding datafiles,
-optimize/replace archive redolog files on separated filesystem from ORACLE_BASE
- separating auditing log files from $ORACLE_BASE to own filesystem
- separating diag directory on separated file system ( logging, tracing )
- adding/enlarging TEMP ts
- adding/enlarging undo
- enlarging redo for higher transaction rate ( to reduce number of switched per time perceived in alert_SID.log )
- adding online redo and control files mirrors
So in this context try to inspect content of the disk space from the highest logical level in V$, DBA views down to fdisk partitions.
The idea was to go in these steps:
1. select paths of present online redo groups, datafiles, controlfiles, temp, undo
   from V$, dba views
2. For the paths got from the step 1
   locate filesystems and for those filesystems inspect which are on logical volumens and which are directly on partitions.
3. For all used logical volumes locate the logical partitions and their disks /dev/sda, /dev/sdb, ...

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.

10g ASM on Logical Volumes vs. Raw devices and SAN Virtualization

We are looking at setting up our standards for Oracle 10g non-rac systems. We are looking at the value of Oracle ASM in our environment.
As per the official Oracle documentation, raw devices are preferred to using Logical Volumes when using ASM.
From here: http://download.oracle.com/docs/cd/B19306_01/server.102/b15658/appa_aix.htm#sthr
ef723
"Note: Do not add logical volumes to Automatic Storage Management disk groups. Automatic Storage Management works best when you add raw disk devices to disk groups. If you are using Automatic Storage Management, then do not use LVM for striping. Automatic Storage Management implements striping and mirroring."
Also, as per Metalink note 452924.1:
"10) Avoid using a Logical Volume Manager (LVM) because an LVM would be redundant."
The issue is: if we use raw disk devices presented to ASM, the disks don't show up as used in the unix/AIX system tools (i.e. smit, lspv, etc.). Hence, when looking for raw devices on the system to add to filesystems/volume groups/etc., it's highly possible that a UNIX admin will grab a raw device that is already in use by Oracle ASM.
Additionally, we are using a an IBM DS8300 SAN with IBM SAN Volume Controller (SVC) in front of it. Hence, we already have storage virtualization and I/O balancing at the SAN/hardware level.
I'm looking for a little clarification to the following questions, as my understanding of their responses seem to confict:
QUESTION #1: Can anyone clarify/provide additional detail as to why Logical volumes are not preferred when using Oracle ASM? Does the argument still hold in a SAN Virtualized environment?
QUESTION #2: Does virtualization at the software level (ASM) make sense in our environment? As we already have I/O balancing provided at the hardware level via our SVC, what do we gain by adding yet another level of I/O balancing at the ASM level? Or as in the
arguments the Oracle documentation makes against using Lvm, is this an unnecessary redundant striping (double-striped or in our case triple-striped/plaid)?
QUESTION #3: So does SAN Virtualization conflict or compliment the virtualization provided by ASM?

After more research/discussions/SR's, I've come to the following conclusion.
Basically, in an intelligent storage environment (i.e. SVC), you're not getting a 100% bang for the buck by using ASM. Which is the cat's meow in a commodity hardware/unintelligent storage environment.
Using ASM in a SVC environment potentially wastes CPU cycles having ASM balance i/o that is already balanced on the backend (sure if you shuffle a deck of cards that are already shuffled you're not doing any harm, but if they're already shuffled - then why are you shuffling them again??).
That being said, there may still be some value for using ASM from the standpoint of storage management for multiple instances on a server. For example, one could better minimize space wastage by being able to share a "pool" of storage between mulitiple instances, rather than having to manage space on an instance-by-instance (or filesystem by filesystem) level.
Also, in the case of having a unfriendly OS where one is unable to dynamically grow a filesystem (i.e. database outage required), there would be a definite benefit provided by ASM in being able to dynamically allocate disks to the "pool". Of course, with most higher-end end systems, dynamic filesystem growth is pretty much a given.
In the case of RAC, regardless of the backend, ASM with raw is a no-brainer.
In the case of a standalone instance, it's a judgement call. My vote in the case of intelligent storage where one could dynamically grow filesystems, would be to keep ASM out of the picture.
Your vote may be different....just make sure you're putting in a solution to a problem and not a solution that's looking for a problem(s).
And there's the whole culture of IT thing as well (i.e. do your storage guys know what you're doing and vice versa).....which can destroy any technological solution, regardless of how great it is.

WebStart Flash and Veritas Volume Manager

I would like to use WebStart Flash for backup of the system
disk. The goal is to be able to recover the system disk rapidly.
It works perfectly for systems without Veritas Volume
Manager on the system disk.
However, if Veritas Volume Manager is installed and used
for mirroring the root disk, the system is not able to boot using
WebStart Flash. This is probably because the "private region"
of the disk is not included in the flash archive.
Does anybody have a solution for this, or does any of
you successfully combine WebStart Flash and Veritas
Volume Manager?
I use Jumpstart and the install_type is configured to
flash_install.
The question was also asked in the newsgroup
comp.unix.solaris.
Rgds,
Henrik

For many reasons, today you cannot save the VxVM
private region information as an implicit part of a
flash archive. The procedure would likely be to
unencapsulate the root drive, create the flash archive,
then re-encapsulate the root drive. This is an ugly
procedure and may cause more pain than it is worth.
When a root disk is encapsulated, an entry is put
into the /etc/system file which says to use the VxVM
or SVM logical volume for the rootdev rather than
the actual device from which the system was originally
booted. When you create a flash archive, this modification
to the /etc/system is carried along. But, when you install
it on a new system which doesn't have VxVM properly
installed already (a chicken-and-the-egg problem)
then the change of the rootdev to the logical volume
will fail. The result is an unbootable system (without
using 'boot -a' and pointing to a different /etc/system
file like /dev/null).
The current recommended process is to use a prototype
system which does not have an encapsulated root
to create the flash archive.
VxVM also uses the ELM license manager which will
tie the VxVM runtime license to the hostid. This makes
moving flash archives with VxVM to other machines
impractical or difficult.
The long term solution would be to add logical volume
management support to the JumpStart infrastructure.
I'm not counting on this anytime soon :-(
-- richard

Volume Manager

We are connecting a Sun 3500 to an HP VA7400 storage device, we require redundant paths to our volumes and it has been suggested that we need to purchase Veritas Logical Volume Manager, can we accomplish the above using Solstice Disk Manager? Any advice would be greatly appreciated as we are brand new to Sun servers.

Yes! Solstice Disk Suite can be used instead of Veritas Volume Manager.
I have never come across the HP VA7400 storage so can not comment on how to do it. Have HP qualified this storage for use with Sun Cluster?

SE3511 - recovering logical volumes

Hi ,
I have a SE3511 array with one controller array and a JBOD both are fully populated with 400GB disks. There is one each logical drives(RAID5) configured on both controller array and JBOD. Each logical drives were divided into two logical volumes of equal size. SO I had 4 logical volumes total. After doing a physical move of the array to different location, I had some problems witht the array. When I checked the configuration, i could see all the logical volumes are disappeared, but still the logical drives are there. Unfortunately I didn't take a configuration backp of the styorage. But I know the size of the logical volumes.
Can any body help how to recover the lost logical volumes or create the logical volumes without losing data.
Thanks
Babu

Found the following:-
http://download.oracle.com/docs/cd/B19306_01/server.102/b14239/manage_ls.htm#sthref1308
Oracle® Data Guard Concepts and Administration
10g Release 2 (10.2)
Part Number B14239-04
Managing A Logical Standby Database -- 9.5.4
Indicates that the Logical Standby can recover through an OPEN RESETLOGS if its running in flashback database mode.
Not sure what the impact of this is on non-guarded components - could be that if it flashes the logical back too that it loses all the non-guarded components

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.

Logical Volume is non-contiguous

I'm having problems creating database files on a certain logical volume. It is configured non-contiguous. Does this matter?

connect / as SYSDBA
set echo on
spool /u02/app/oracle/admin/mmstus/create/crt_mmstus.log
startup nomount pfile="$ORACLE_HOME/dbs/initMMSTUS.ora";
CREATE DATABASE MMSTUS
MAXINSTANCES 1
MAXLOGHISTORY 1
MAXLOGFILES 255
MAXLOGMEMBERS 5
MAXDATAFILES 1024
DATAFILE '/u03/oradata/MMSTUS/system01.dbf' SIZE 2048M
AUTOEXTEND ON NEXT 1024M MAXSIZE 4096M
EXTENT MANAGEMENT LOCAL
DEFAULT TEMPORARY TABLESPACE TEMP
TEMPFILE '/u03/oradata/MMSTUS/temp01.dbf' SIZE 2048M
AUTOEXTEND ON NEXT 1024M MAXSIZE 4096M
UNDO TABLESPACE "UNDOTBS1"
DATAFILE '/u03/oradata/MMSTUS/undotbs01.dbf' SIZE 2048M
AUTOEXTEND ON NEXT 1024M MAXSIZE 4096M
CHARACTER SET AL32UTF8
NATIONAL CHARACTER SET AL16UTF16
LOGFILE GROUP 1 ('/u02/oralog/MMSTUS/mmstus_redo1_1A.log',
'/u03/oralog/MMSTUS/mmstus_redo1_1B.log') SIZE 100M ,
GROUP 2 ('/u02/oralog/MMSTUS/mmstus_redo1_2A.log',
'/u03/oralog/MMSTUS/mmstus_redo1_2B.log') SIZE 100M ,
GROUP 3 ('/u02/oralog/MMSTUS/mmstus_redo1_3A.log',
'/u03/oralog/MMSTUS/mmstus_redo1_3B.log') SIZE 100M ,
GROUP 4 ('/u02/oralog/MMSTUS/mmstus_redo1_4A.log',
'/u03/oralog/MMSTUS/mmstus_redo1_4B.log') SIZE 100M ,
GROUP 5 ('/u02/oralog/MMSTUS/mmstus_redo1_5A.log',
'/u03/oralog/MMSTUS/mmstus_redo1_5B.log') SIZE 100M ,
GROUP 6 ('/u02/oralog/MMSTUS/mmstus_redo1_6A.log',
'/u03/oralog/MMSTUS/mmstus_redo1_6B.log') SIZE 100M ,
GROUP 7 ('/u02/oralog/MMSTUS/mmstus_redo1_7A.log',
'/u03/oralog/MMSTUS/mmstus_redo1_7B.log') SIZE 100M ,
GROUP 8 ('/u02/oralog/MMSTUS/mmstus_redo1_8A.log',
'/u03/oralog/MMSTUS/mmstus_redo1_8B.log') SIZE 100M ;
spool off
exit;
The init.ora file has db_name=MMSTUS

Reformatted Mac HD but it no longer has a Logical Volume Group

Hi Guys,
I've reformatted my Mac Pro's main HD, prior to doing a completely new install of Yosemite.
Having reformatted it, I noticed that in the Disk Utility, there is no longer a main hard drive at the top of the list called Macintosh HD, with a Logical Partition (below it) also called Macintosh HD.
Instead, the main hard drive is now called by it's SSD product name, which is 1 TB Apple SSD SM10... (etc). When I highlight it, the description in the bottom of the Disk Utility window is the same (1 TB Apple SSD...), whereas it used to be called Macintosh HD and its 'type' a Logical Volume Group.
I have also noticed also that drive beneath it, Macintosh HD, is not referred to in the description as a Logical Partition now, whereas originally it was. (I've been able to make the above comparisons using my MacBook, which has never been formatted since purchase.)
My questions are:
- Is there a problem in not having a Logical Volume Group, but instead just having the hard drive specs as the name?
- If this IS a problem, what is the best way to restore the drive so that I have a Logical Volume Group and a Logical Partition, both called Macintosh HD?
If anyone can help me out with a layman's understanding of why reformatting my hard drive has set things up differently to the original configuration, and what the impacts are, I'd appreciate it!
Cheers,
Mike

Hi there,
Thanks very much for helping out with this, much appreciated.
Here is the info that shows up when I type distil - see below.
Cheers,
Mike
Last login: Sat Mar 21 21:51:41 on console
MJP-iMac:~ MJP$ diskutil
Disk Utility Tool
Utility to manage local disks and volumes
Most options require root access to the device
Usage: diskutil [quiet] <verb> <options>, where <verb> is as follows:
     list                  (List the partitions of a disk)
     info[rmation]         (Get information on a specific disk or partition)
     listFilesystems       (List file systems available for formatting)
     activity              (Continuous log of system-wide disk arbitration)
     u[n]mount             (Unmount a single volume)
     unmountDisk           (Unmount an entire disk (all volumes))
     eject                 (Eject a disk)
     mount                 (Mount a single volume)
     mountDisk             (Mount an entire disk (all mountable volumes))
     enableJournal         (Enable HFS+ journaling on a mounted HFS+ volume)
     disableJournal        (Disable HFS+ journaling on a mounted HFS+ volume)
     moveJournal           (Move the HFS+ journal onto another volume)
     enableOwnership       (Treat as exact User/Group IDs for a mounted volume)
     disableOwnership      (Ignore on-disk User/Group IDs for a mounted volume)
     rename[Volume]        (Rename a volume)
     verifyVolume          (Verify the file system data structures of a volume)
     repairVolume          (Repair the file system data structures of a volume)
     verifyDisk            (Verify the components of a partition map of a disk)
     repairDisk            (Repair the components of a partition map of a disk)
     verifyPermissions     (Verify the permissions of a Mac OS X volume)
     repairPermissions     (Repair the permissions of a Mac OS X volume)
     eraseDisk             (Erase an existing disk, removing all volumes)
     eraseVolume           (Erase an existing volume)
     reformat              (Erase an existing volume with same name and type)
     eraseOptical          (Erase optical media (CD/RW, DVD/RW, etc.))
     zeroDisk              (Erase a disk, writing zeros to the media)
     randomDisk            (Erase a disk, writing random data to the media)
     secureErase           (Securely erase a disk or freespace on a volume)
     partitionDisk         ((re)Partition a disk, removing all volumes)
     resizeVolume          (Resize a volume, increasing or decreasing its size)
     splitPartition        (Split an existing partition into two or more)
     mergePartitions       (Combine two or more existing partitions into one)
     appleRAID <verb>      (Perform additional verbs related to AppleRAID)
     coreStorage <verb>    (Perform additional verbs related to CoreStorage)
diskutil <verb> with no options will provide help on that verb
MJP-iMac:~ MJP$

Solaris Volume Manager or Hardware RAID?

Hi - before I build some new Solaris servers I'd like thoughts on the following please. I've previously built our Sun servers using SVM to mirror disks and one of the reasons is when I O/S patch the server I always split the mirrors beforehand and in the event of a failure I can just boot from the untouched mirror - this method has saved my bacon on numerous occasions. However we have just got some T4-1 servers that have hardware RAID and although I like this as it moves away from SVM / software RAID and to hardware RAID I'm now thinking that I will no longer have this "backout plan" in the event of issues with the O/S updates or otherwise however unlikely.
Can anyone please tell me if I have any other options?
Thanks - Julian.

Thanks - just going through the 300 page ZFS admin guide now. I want to ditch SVM as it's clunky and not very friendly whenever we have a disk failure or need to O/S patch as mentioned. One thing I have just read from the ZFS admin guide is that:
"As described in “ZFS Pooled Storage” on page 51, ZFS eliminates the need for a separate volume
manager. ZFS operates on raw devices, so it is possible to create a storage pool comprised of
logical volumes, either software or hardware. This configuration is not recommended, as ZFS
works best when it uses raw physical devices. Using logical volumes might sacrifice
performance, reliability, or both, and should be avoided."
So looks like I need to destroy my hardware RAID as well and just let ZFS manage it all. I'll try that, amend my JET template and kick of an install and see what it looks like.
Thanks again - Julian.

How does logical volume helps in performance in AIX..Should have posted IBM

We are setting up a new DB server and the disks are in RAID5 config,Does putting data and index in different logical volumes helps in performance

(I hope I'm not falling for April Fools joke here...)
Hi Maran,
As someone already answered, if both volumes are striped against all available disks, you can put everything in one volume and expect equal or better performance.
However, I want to warn you from optimizing the disk structure without knowing that your database will really bottleneck on disk access to index and data blocks. My storage manager and I wasted countless hours with such optimizations before realizing that we are wasting our time because the application code contains so many functions that disk IO is not even close to being an issue.
-- Chen

Extend logical volume using diskpart on hardware RAID-5 logical drive in 2003 R2 server

Hi,
Can somebody help me.I have succesfully completed my RAID-5 expansion by adding 1 hard drive to the RAID-5 array using HP ACU. I just want to confirm whether I can use diskpart utility to extend my logical volume. Since the Disk management gui does not have
any extend option.

Hi,
Any update?
Just checking in to see if the suggestions were helpful. Please let us know if you would like further assistance.
Best Regards,
Andy Qi
TechNet Subscriber Support
If you are
TechNet Subscription user and have any feedback
on our support quality, please send your feedback here.
Andy Qi
TechNet Community Support

Solaris9 Logical Volume Manager

Similar Messages

Maybe you are looking for