11-28-2016
Quote:
Originally Posted by
lckdanny
As you said that, when using SAN, there have no improvement to use striping?
Basically and in most cases: yes. There are some notable exceptions to this rule (see Scrutinizers post #10 for such exceptions), but in general: what you try to achieve with disk striping a modern SAN box already does itself internally. There is no sense in doing it twice. If you are particularly unlucky (well, i agree, this is more a theoretical possibility) your own striping and the striping of the SAN box will overlay and create a Moiré-like effect that de-stripes your disk access.
I have once written a lengthy
article about performance tuning, which i suggest you to read. Maybe it answers a few questions you might have.
The VNX is a small platform and i haven't worked with it but i suppose its frontend is not all that sophisticated. Therefore it might be worthwile to examine other aspects of disk access as well if the need of performance tuning arises: queue sizes, the distribution of block sizes in your typical load, data hotspots (maybe suggesting multitiered disk architectures with SATA-disks on one end and FC-disks or even SSDs on the other) or some other measures.
As Scrutinizer said so rightly: in performance tuning it always depends and one size never fits all.
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
LEARN ABOUT HPUX
vxsplitlines
vxsplitlines(1M) vxsplitlines(1M)
NAME
vxsplitlines - show disks with conflicting configuration copies in a cluster
SYNOPSIS
vxsplitlines [-g diskgroup] [-c daname]
DESCRIPTION
If you import portions of a disk group on different systems, this can lead to conflicting configuration copies on the disks of the disk
group.
If the configuration information in a disk group is ambiguous, it may not be possible for Veritas Volume Manager to determine which config-
uration copy is most up-to-date. (This is usually termed a serial split brain (SSB) condition when it occurs in a cluster.) You cannot
import a disk group in this state unless you specify which disk's configuration copy to use.
You can use the vxsplitlines command to see which disks in a disk group have conflicting configuration copies, and use this information
together with your knowledge of the history of the disk groups' usage to determine which configuration copy is most valid.
The output from vxsplitlines displays the vxdg commands that you can run to import the disk group using the available configuration copies.
The -o selectcp option of the vxdg import command is used to select the configuration copy to use for the import.
OPTIONS
-c daname Display the SSB IDs for each disk that are stored in the configuration copy on the disk specified by its disk access name.
Note: Although the SSB IDs for some disks may match, this does not necessarily mean that those disks' configuration copies have
recorded all the configuration changes. When viewed from some other configuration copies, the SSB IDs of the same disks may not
match.
-g diskgroup
Specifies the disk group. If a disk group is not specified, the default disk group is used as determined from the rules on the
vxdg(1M) manual page.
EXAMPLES
Display the disks on each side of the split in the disk group newdg:
vxsplitlines -g newdg
Display the SSB IDs stored in the configuration copy on disk c2t4d0:
vxsplitlines -g newdg -c c2t4d0
NOTES
The vxsplitlines is primarily intended to be used with private disk groups, but it also works with shared disk groups.
The version number of the disk group must be 110 or greater.
SEE ALSO
vxdg(1M)
Veritas Volume Manager Administrator's Guide
VxVM 5.0.31.1 24 Mar 2008 vxsplitlines(1M)