11-19-2008
Quote:
Originally Posted by
funksen
[...]well it's no problem on non concurrent vgs, [...]
Sorry, I thought you asked about concurrent VG.
Quote:
Originally Posted by
funksen
[...]extending with new luns is the way we were doing it the last years, but this leads to 100+ luns on bigger systems[...]
yes, that happens usually when the hdisk slices from the SAN are too small. I remember a datacenter where the SAN guys allocated the SAN disks in 8GB chunks because "with smaller disks we are more flexible".... I.e. know your workload from the beginning. If your data doubles every 6 month or so start with few big disks/lun so that you neither hit the VG limits nor end up with hundreds of disks/luns (that might double when mirrored).
10 More Discussions You Might Find Interesting
1. UNIX for Advanced & Expert Users
Hi,
I notice in my Sun Solaris 8 sparc workstatin, I am able to login concurrently using a same user ID.
Is there a way to disallow this? That is, at anyone time, the user can have only 1 login session.
How can it be done?
Thanks (10 Replies)
Discussion started by: champion
10 Replies
2. Shell Programming and Scripting
Hi
I have a ksh that can have multiple instances running at the same time.
The script (each instance) uses the SAME log file to write to.
Should this cause a problem or is the ksh clever enough to queue write requests to the file?
Thanks.
GMMIKE (2 Replies)
Discussion started by: GNMIKE
2 Replies
3. IP Networking
Just like concurrent tcp server, anyone know how to design the concurrent udp server with the thread? it's best to give some basic examples,thanks (0 Replies)
Discussion started by: Frank2004
0 Replies
4. AIX
have machine running AIX 4.3.3ML 11. It's rootvg has about 1GB of space available and is made up of 2 9GB drives. We are going to upgrade it to AIX 5.x but wanted more disk space for the upgrade. So was going to install 2 new 18GB drives. The plan was to bring the 2 18GB drives in as hdisk# and... (2 Replies)
Discussion started by: spattson
2 Replies
5. Shell Programming and Scripting
We have a very large text file..contains almost 100K lines.
We want to process this file to generate another text file as per our data requirement.
As for now the parsing of data takes 20-25 mins each , for 100K lines.
the current script uses :
While Read Each Line
do parsing..
Done
... (6 Replies)
Discussion started by: Amruta Pitkar
6 Replies
6. Linux
Hi Guys,
I just wondering if any of the AIX gurus with some exposure to Linux Redhat can tell me whether in Linux ( Red Hat or OpenSuse ) we have a similar option/capability like the CIO (Concurrent I/O) which is currently available on AIX. The reason I'm asking is because in the past we... (2 Replies)
Discussion started by: arizah
2 Replies
7. Shell Programming and Scripting
Hi all,
I have a folder with sql files that need to be inserted in a DB with SQL*Plus. The thing is that it takes too long to insert them all one by one, so I want to insert them five at a time.
Currently what I use is this:
for $FILENAME in *.sql
do
sqlplus -s $DBUSER@$SID << EOF
... (0 Replies)
Discussion started by: Tr0cken
0 Replies
8. Solaris
Hi all,
I've been tasked to create a robot account across a bunch of SunOS servers, amongst the requirements for this account is this condition:
Concurrent access requirement
The robot account shall have the ability to create at least ten(10) concurrent access sessions. In order to... (0 Replies)
Discussion started by: dan-e
0 Replies
9. AIX
Hi All,
I am going to perform some activity in 2Node HA Server(Active/Passive).
For that i have to do some pre-requsite (ie., Resource Group VG's should be Enhanced-Concurrent)
In my setup, we have two volume groups in one RG. In that one VG is Normal and another is Enhance Concurrent.
... (2 Replies)
Discussion started by: Thala
2 Replies
10. AIX
Hi,
What are the differences between concurrent and enhanced concurrent VGs.?
Any advantages of enhanced concurrent VG over normal concurrent vg
Regards,
Siva (2 Replies)
Discussion started by: ksgnathan
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)