11-25-2008
Quote:
Originally Posted by
pobman
was not sure about the PP though how can I tell what I should use? So I left it as 32MB
When a disk is added to a VG it is divided in parts the size of PPsize.
So you can tell by applying LVM restrictions: a single disk can hold max. 1019 PPs. If you have disks approximately 32GB in size you can go with a PP size of 32MB, arriving at ~1000 PPs per disk. If your disks are considerably larger than this you would only be able to use the first 32GB (1019x32MB to be exact) of the disk, losing the rest of it.
Since it is a good idea of leaving room for expansion everywhere consider using a PP size which divides the disk in 200-500 parts. For example: for 72GB disks use a PP size of 256MB giving ~300 PPs. This would allow for the use of disks up to 260GB without losing space.
I hope this helps.
bakunin
8 More Discussions You Might Find Interesting
1. UNIX for Dummies Questions & Answers
Hi. I have a situation here where I need to backup a users' home directory and restore onto another server. The issue here is that both servers have different operating systems and I am looking for advices on how to proceed.
The source server operating system is Tru64 v5.1, and here's the output... (1 Reply)
Discussion started by: fidodido
1 Replies
2. AIX
Hi all,
I am still working on my mksysb restore.
My latest issue is during an alt_disk_install from tape I got the following error after all the data had been restored.
0505-143 alt_disk_install: Unable to match mksysb level 5.2.0 with any
available boot images. Please correct this... (0 Replies)
Discussion started by: pobman
0 Replies
3. Shell Programming and Scripting
Hi all,
I have the following script, but are not too sure about the syntax to complete the script.
In essence, the script must connect to a SFTP server at a client site with username and password located in a file on my server.
Then change to the appropriate directory.
Pull the data to the... (1 Reply)
Discussion started by: codenjanod
1 Replies
4. HP-UX
Hi all,
I have a server running HP-UX 11i V1 (11.11).
We had a problem with the system disk which cannot boot and the recovery with the CD failed too.
the only solution was to re-install the system on a new disk.
The problem now is to get access to the data which are on other disks, not... (2 Replies)
Discussion started by: aribault
2 Replies
5. SCO
Our company purchased a spare HP ML350 server - identical to current one in use to act as minimal downtime replacement should the inevitable happen.
After install of OS 5.0.7 and restore of cpiobackup I get this message:
-: Syntax error: Hostname= $inexpected
The SCO licence policy... (4 Replies)
Discussion started by: moondogi
4 Replies
6. Solaris
Hi guys
i tried to restore a server from a ufsdump. For your information, the ufsdump was created on a v440 and i have to restore it to a v240... is it supported? should it work? don't know but i try!
the problem is after restoring the filesystem, modify the vfstab, system file and install... (5 Replies)
Discussion started by: beta17
5 Replies
7. Emergency UNIX and Linux Support
Hi,
One of my Linux server running Redhat version 3 is dead. I already build the new server but I need to get few of the license files from the old server. Currently, I booted the old server using the CDROM. But when I go to /mnt/sysimage/var, I don't see any of files? I also went to... (4 Replies)
Discussion started by: samnyc
4 Replies
8. Shell Programming and Scripting
Hi Folks, I have taken a backup of root filesystem with tar. Please help me to write a ksh script to automate restoration and root mirror in solaris 10.
Thanks in advance. (1 Reply)
Discussion started by: wills
1 Replies
LEARN ABOUT DEBIAN
mkqdisk
mkqdisk(8) Quorum Disk Management mkqdisk(8)
NAME
mkqdisk - Cluster Quorum Disk Utility
WARNING
Use of this command can cause the cluster to malfunction.
SYNOPSIS
mkqdisk [-?|-h] | [-L] | [-f label] [-c device -l label] [-d [-d ...]]
DESCRIPTION
The mkqdisk command is used to create a new quorum disk or display existing quorum disks accessible from a given cluster node.
OPTIONS
-c device -l label
Initialize a new cluster quorum disk. This will destroy all data on the given device. If a cluster is currently using that device
as a quorum disk, the entire cluster will malfunction. Do not run this on an active cluster when qdiskd is running. Only one
device on the SAN should ever have the given label; using multiple different devices is currently not supported (it is expected a
RAID array is used for quorum disk redundancy). The label can be any textual string up to 127 characters - and is therefore enough
space to hold a UUID created with uuidgen(1).
-f label
Find the cluster quorum disk with the given label and display information about it.
-L Display information on all accessible cluster quorum disks.
-d Increase debugging level. Specify multiple times for more information. Currently, specifying more than twice has no effect.
SEE ALSO
qdisk(5), qdiskd(8), uuidgen(1)
July 2006 mkqdisk(8)