02-22-2011
well if you write to ONE lun - its slower than if you write to 10 luns in parallel as AIX simply doesnt care about what is behind the adapters.
Real life experience about a year ago - attaching my 124 luns - 33 GB each - from one to 3 pairs of hba's and changing the 4 DB filesystems from minimum to maximum distribution across the disks - improved our EOD batch (oracle) from 3.5 hrs to 14 min.
Regards
zxmaus
10 More Discussions You Might Find Interesting
1. AIX
Hi, I was told that 300GB of LUN has been allocated to my server by the SAN group. apart from rootvg i have 2 volume groups(oracle) for which i need to add space as follows:
oradbvg 250GB to be added
oralvg 50GB
what are the steps that i should follow after iam being told that LUN has been... (4 Replies)
Discussion started by: karthikosu
4 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. UNIX for Dummies Questions & Answers
I need to concatenate about a thousand files (using a loop) on a UNIX server. Also, each file has a header row which is to be removed. Which of the following would give better performance?
tail+2 <filename> or sed '1,1d' <filename>
Or is there another, faster way?
Thanks,
Kaus (4 Replies)
Discussion started by: kausmone
4 Replies
4. UNIX for Dummies Questions & Answers
Hi guys,
what is the relation between I/O performance and file systems.
I have a file systems called /dcs/data01 which is having 4Tb size.
According our application we can split the file system like
dcs/data01 -> 1Tb
dcs/data02 -> 1Tb
dcs/data03 -> 1Tb
dcs/data04 -> 1Tb
do you... (4 Replies)
Discussion started by: Davinzy
4 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
Hola a todos, me gustaría saber cómo chequear si estas LUN´s
objecthexuid .........................: 6005-08b4-0001-529c-0005-6000-45d6-0000
objecthexuid .........................: 6005-08b4-0001-529c-0005-6000-45d9-0000
objecthexuid .........................:... (1 Reply)
Discussion started by: aav1307
1 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. UNIX for Dummies Questions & Answers
hi,
I want to create a volume group of 200 GB and then create different file systems on that.
please help me out. Its becomes confusing when the PP calculating PP.
I don't understand this concept. (2 Replies)
Discussion started by: kamaldev
2 Replies
9. Solaris
So,
We have a Netapp storage solution. We have Sparc T4-4s running with LDOMS and client zones in the LDOMS, We are using FC for storage comms. So here's the basic setup
FC luns are exported to the primary on the Sparc box. using LDM they are then exported to the LDOM using vdisk. at the... (4 Replies)
Discussion started by: os2mac
4 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
SG_LUNS(8) SG3_UTILS SG_LUNS(8)
NAME
sg_luns - send the SCSI REPORT LUNS command
SYNOPSIS
sg_luns [--decode] [--help] [--hex] [--maxlen=LEN] [--quiet] [--raw] [--select=SR] [--verbose] [--version] DEVICE
DESCRIPTION
Send the SCSI REPORT LUNS command to the DEVICE and outputs the response. In the SPC-3 SCSI standard support for this command is mandatory.
OPTIONS
Arguments to long options are mandatory for short options as well.
-d, --decode
decode logical unit numbers into their hierarchical parts. Interprets luns as described in SAM-3 when the HiSup bit is set in a
standard INQUIRY's response.
-h, --help
output the usage message then exit.
-H, --hex
output response to this command in ASCII hex.
-m, --maxlen=LEN
where LEN is the (maximum) response length in bytes. It is placed in the cdb's "allocation length" field. If not given (or LEN is
zero) then 65536 is used. The maximum value of LEN is 65536.
-q, --quiet
output ASCII hex rendering of each report lun, one per line.
-r, --raw
output response in binary (to stdout).
-s, --select=SR
this option sets the 'select report' field (SR) in the SCSI REPORT LUNS command. The default value is 0. When 0 is given (or this
option is not specified) then the DEVICE should yield a list of luns addressable via this "I_T nexus" that use the following lun
addressing methods: logical unit addressing, peripheral device addressing and flat space addressing. When 1 is given the DEVICE
should yield a list of only "well known" logical units addressable via this "I_T" nexus. When 2 is given the DEVICE should yield all
luns addressable via this "I_T" nexus. To simplify, for the I_T nexus associated with the DEVICE, the meanings of the SR values
are:
0 : all luns excluding well known logical units
1 : well known logical units
2 : all luns
Values greater than 2 are reserved (at SPC-4 (rev 8)).
-v, --verbose
increase the level of verbosity, (i.e. debug output).
-V, --version
print the version string and then exit.
EXIT STATUS
The exit status of sg_luns is 0 when it is successful. Otherwise see the sg3_utils(8) man page.
AUTHORS
Written by Douglas Gilbert.
REPORTING BUGS
Report bugs to <dgilbert at interlog dot com>.
COPYRIGHT
Copyright (C) 2004-2008 Douglas Gilbert
This software is distributed under a FreeBSD license. There is NO warranty; not even for MERCHANTABILITY or FITNESS FOR A PARTICULAR PUR-
POSE.
SEE ALSO
sg_inq(8)
sg3_utils-1.26 April 2008 SG_LUNS(8)