04-17-2008
I think i have told you already in the other thread the concept of PPs and PP size.
The value is freely selectable upon creation of the VOLUME GROUP, not the LUN. However it limits your disk size as well as the total capacity of the Volume Group you create: maximum 1019 PPs per PV (=hdisk device) and maximum 32 PVs per VG.
Since you plan to create only one PV (as you said in the other thread) you should select the PP size so that you are not near the 1019 PPs per PV limit.
Example: If the LUN is, say, 50GB in size you should use a PP size of 256MB or 512MB if no other aspects apply.
This way you will be able to use LUNs of up to roughly 250 (500) GB in size giving you a theoretical total of approx. 8 (16) TB in the VG. This should be enough space to grow into for most practical purposes when right now your VGs data fit into the 50 GB i based my example on.
I hope this helps.
bakunin
10 More Discussions You Might Find Interesting
1. Filesystems, Disks and Memory
Hi,
How can i monitoring the LUN in HP Storage with korn shells? I would like to have a shell can monitoring the LUN, VGs, lvols and raw devices.
Jesus (3 Replies)
Discussion started by: jgutierrez29
3 Replies
2. HP-UX
Hi, This is my first post and I hope I can present my questions the right way. I am going to be asked to create logical volumes for a Hitachi SAN device on a New HP 11 server. Currently, They are running their data on a EMC (prod server). They are looking to convert the data and filesystems over to... (3 Replies)
Discussion started by: Uni-dev
3 Replies
3. Filesystems, Disks and Memory
Hi
Iīm new to san and lunīs
I see the disks, but are not able to mount them
bash-3.00# mountall
checking ufs filesystems
/dev/rdsk/c3t5006016930601F86d0s6: I/O error
Can't open /dev/rdsk/c3t5006016930601F86d0s6: I/O error
/dev/rdsk/c3t5006016930601F86d0s6: CAN'T CHECK FILE SYSTEM.... (1 Reply)
Discussion started by: ludvig
1 Replies
4. AIX
Hi team,
2E493F13 0612155010 P H dac0 ARRAY OPERATION ERROR
2E493F13 0612155010 P H dac0 ARRAY OPERATION ERROR
2E493F13 0612155010 P H dac0 ARRAY OPERATION ERROR
2E493F13 0612154910 P H dac0 ARRAY OPERATION ERROR
2E493F13 0612154910 P H dac0 ... (4 Replies)
Discussion started by: kkeng808
4 Replies
5. HP-UX
In HP-UX, VLM: what volume group, are these LUNs? anyone know ?
objecthexuid .........................: 6005-08b4-0001-529c-0005-6000-45d6-0000
objecthexuid .........................: 6005-08b4-0001-529c-0005-6000-45d9-0000
objecthexuid .........................:... (5 Replies)
Discussion started by: aav1307
5 Replies
6. Linux
Hi,
I have presented a new 70GB LUN to my RedHat Linux VM server. How do I rescan for the new LUN?
Thanks,
Sparcman:confused: (2 Replies)
Discussion started by: sparcman
2 Replies
7. Red Hat
Hi guys I have been asked for the following:
SMI Oracle database PTP10 Oracle 10g RAC on usdfslprac4 and usdfslprac5 Linux boxes is reaching its space limit. It is just 20 GB away from being completely out of disk space. And then database will stop working and SMI system hence will be impacted.... (0 Replies)
Discussion started by: 300zxmuro
0 Replies
8. Solaris
how to create luns plzzzzzz (1 Reply)
Discussion started by: nsusheelgoud
1 Replies
9. Red Hat
In Solaris the administrator has to update /kernel/drv/sd.conf file to tell the sd driver to scan for a broader range of scsi devices.
Can someone please tell me what file needs to be update in Redhat Linux 5 for the same.
Second part of the question is WWN for HBA's can be found (atleast in my... (1 Reply)
Discussion started by: Tirmazi
1 Replies
10. Solaris
running Solaris10 with Qlogic FC adapters connected to a multi-host FC array..using VXFS/VXVM..
Is there in Solaris10 or using some Qlogic drivers to filter out only the LUNs this host can see ??
Normally this is done by LUN masking in the FC switch or the FC array itself..however, neither... (2 Replies)
Discussion started by: ppchu99
2 Replies
LEARN ABOUT HPUX
prealloc
prealloc(1) General Commands Manual prealloc(1)
NAME
prealloc - preallocate disk storage
SYNOPSIS
name size
DESCRIPTION
preallocates at least size bytes of disk space for an ordinary file name, creating the file if name does not already exist. The space is
allocated in an implementation-dependent fashion for fast sequential reads and writes of the file.
fails and no disk space is allocated if name already exists and is not an ordinary file of zero length, if insufficient space is left on
disk, or if size exceeds the maximum file size or the file size limit of the process (see ulimit(2)). The file is zero-filled.
DIAGNOSTICS
returns one of the following values upon completion:
0 Successful completion.
1 name already exists and is not an ordinary file of zero length.
2 There is insufficient room on the disk.
3 size exceeds file size limits.
EXAMPLES
The following example preallocates 50000 bytes for the file
WARNINGS
Allocation of file space is highly dependent on current disk usage. A successful return does not indicate how fragmented the file actually
might be if the disk is approaching its capacity.
AUTHOR
was developed by HP.
SEE ALSO
prealloc(2), ulimit(2).
prealloc(1)