11-25-2016
I suggest to get rid of the ridiculous striping at all. Striping is a good idea if you hae physical disks and want to spread the load over all of them so that the overall response time of the (disk sub-)system gets better. It makes absolutely no sense at all with SAN disks (from the names of the hdisk devices i suppose you have an EMC storage).
To tell you the bad news up front: you will need a downtime to do this because it means deleting and recreating the LV. Still it is a good idea to do so because the further administration will be way easier once you did it.
I hope this helps.
bakunin
10 More Discussions You Might Find Interesting
1. AIX
Hi All,
I am new to AIX.
I need to extend one Logical Volume it is jfs type on On AIX 5.1.
I have enough free space on the volume group for this extension
Can I use smitty chjfs , will this do it without interruptions to the application that is using this Logical Volume.
Thanks
Scampi (1 Reply)
Discussion started by: scampi
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
Hi,
Smit "Increase the Size of a Logical Volume" command failed. Output:
----------------------------------------------------------
Command: failed stdout: yes stderr: no
Before command completion, additional instructions may appear below.
The distribution of this command (111) failed on... (2 Replies)
Discussion started by: vilius
2 Replies
4. 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
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. HP-UX
Background:
# uname -a
HP-UX deedee B.11.23 U ia64 4294967295 unlimited-user license
deedee.rsn.hp.com:/
# bdf /opt
Filesystem kbytes used avail %used Mounted on
/dev/vg00/lvol6 6553600 6394216 158144 98% /opt
/opt is almost full... (3 Replies)
Discussion started by: Rob Sandifer
3 Replies
7. 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
8. HP-UX
Want to extend the /home filesystem:
Filesystem kbytes used avail %used Mounted on
/dev/vg00/lvol4 262144 260088 2056 99% /home
root@server:./root # vgdisplay vg00
--- Volume groups ---
VG Name /dev/vg00
VG Write Access read/write
VG Status available
Max LV 255
Cur LV 11
Open... (4 Replies)
Discussion started by: proactiveaditya
4 Replies
9. 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
10. 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
CCD(4) BSD Kernel Interfaces Manual CCD(4)
NAME
ccd -- Concatenated disk driver
SYNOPSIS
pseudo-device ccd [count]
DESCRIPTION
The ccd driver provides the capability of combining one or more disks/partitions into one virtual disk.
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.
Note that the 'raw' partitions of the disks must not be combined. Each component partition should be offset at least one cylinder from the
beginning of the component disk. This avoids potential conflicts between the component disk's disklabel and the ccd's disklabel. The kernel
will only allow component partitions of type FS_CCD. But for now, it allows partition of all types since some port lacks support of an on-
disk BSD disklabel. The partition of FS_UNUSED may be rejected because device driver of component disk will refuse it.
In order to compile in support for the ccd, you must add a line similar to the following to your kernel configuration file:
pseudo-device ccd 4 # concatenated disk devices
The count argument is how many ccds memory is allocated for at boot time. In this example, no more than 4 ccds may be configured.
A ccd may be either serially concatenated or interleaved. To serially concatenate the partitions, specify the interleave factor of 0.
If a ccd is interleaved correctly, a ``striping'' effect is achieved, which can increase performance. Since the interleave factor is
expressed in units of DEV_BSIZE, one must account for sector sizes other than DEV_BSIZE in order to calculate the correct interleave. The
kernel will not allow an interleave factor less than the size of the largest component sector divided by DEV_BSIZE.
Note that best performance is achieved if all component disks have the same geometry and size. Optimum striping cannot occur with different
disk types.
Also note that the total size of concatenated disk may vary depending on the interleave factor even if the exact same components are concate-
nated. And an old on-disk disklabel may be read after interleave factor change. As a result, the disklabel may contain wrong partition
geometry and will cause an error when doing I/O near the end of concatenated disk.
There is a run-time utility that is used for configuring ccds. See ccdconfig(8) for more information.
WARNINGS
If just one (or more) of the disks in a non-mirrored ccd fails, the entire file system will be lost.
FILES
/dev/{,r}ccd* ccd device special files.
SEE ALSO
config(1), MAKEDEV(8), ccdconfig(8), fsck(8), mount(8), newfs(8)
HISTORY
The concatenated disk driver was originally written at the University of Utah.
BSD
March 5, 2004 BSD