04-12-2016
It makes no sense to create anything else than scalable VGs any more.
On the downside scalable VGs cannot be used in AIX versions prior to 5.3. Should you need to move the VG between such an (already completely) unsupported system and the AIX 6.1 LPAR you are the exception to this rule.
On the upside: everything else. The minimally slower operation of some of the VG-manipulating commands set aside (you probably will not even notice the difference) set aside scalable VG are more flexible, more easily extendable and offer more maximum space.
I hope this helps.
bakunin
10 More Discussions You Might Find Interesting
1. 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
2. AIX
Does anyone have any simple methods for moving a current logical volume from one volume group to another? I do not wish to move the data from one physical volume to another. Basically, I want to "relink" the logical volume to exist in a different volume group. Any ideas? (2 Replies)
Discussion started by: krisw
2 Replies
3. AIX
Hi,
if I do install aix 5.3 on the rootvg of an aix 4.3.3 system (having rootvg and data1vg),
is it possible to varyonvg the data1vg after the installation ?
(any caution ?) (1 Reply)
Discussion started by: astjen
1 Replies
4. Emergency UNIX and Linux Support
Hi,
I am running AIX 5.3 TL8. After a disk failure, one of my mirrored application volumegroups went down. Unfortunately we have quorum switched on on this VG and the defective disk holds the majority.
I have set MISSINGPV_VARYON to TRUE and tried a forced varyon but it's still failing. I... (3 Replies)
Discussion started by: zxmaus
3 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. AIX
Hi,
I have a 2 node Cluster. Which is working in active/passive mode (i.e Node#1 is running and when it goes down the Node#2 takes over)
Now there's this requirement that we need a mount point say /test that should be available in active node #1 and when node #1 goes down and node#2 takes... (6 Replies)
Discussion started by: aixromeo
6 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. 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
10. AIX
I'm trying to change volume group of a disk, I'm setting up a PowerHa cluster and need to create a volume group named caavg_private and assigne it to hdisk3.
what is the right methods (commands) of doing this?
hdisk0 00f9a6dc66a06fcf None ... (1 Reply)
Discussion started by: spiderpig
1 Replies
LEARN ABOUT X11R4
mkfontscale
MKFONTSCALE(1) General Commands Manual MKFONTSCALE(1)
NAME
mkfontscale - create an index of scalable font files for X
SYNOPSIS
mkfontscale [ -b ] [ -s ] [ -o filename ] [ -x suffix ] [ -a encoding ] ... [ -f fuzz ] [ -l ] [ -e directory ] [ -p prefix ] [ -r prefix ]
[ -n prefix ] [ -- ] [ directory ] ...
DESCRIPTION
For each directory argument, mkfontscale reads all of the scalable font files in the directory. For every font file found, an X11 font
name (XLFD) is generated, and is written together with the file name to a file fonts.scale in the directory.
The resulting fonts.scale file should be checked and possibly manually edited before being used as input for the mkfontdir(1) program.
OPTIONS
-b read bitmap fonts. By default, bitmap fonts are ignored.
-s ignore scalable fonts. By default, scalable fonts are read. If -b is set, this flag has the side effect of enabling the reading of
fonts.scale files.
-o filename
send program output to filename; default is fonts.scale if bitmap fonts are not being read, and fonts.dir if they are. If filename
is relative, it is created in the directory being processed. If it is the special value -, output is written to standard output.
-x suffix
exclude all files with the specified suffix.
-a encoding
add encoding to the list of encodings searched for.
-f fuzz
set the fraction of characters that may be missing in large encodings to fuzz percent. Defaults to 2%.
-l Write fonts.dir files suitable for implementations that cannot reencode legacy fonts (BDF and PCF). By default, it is assumed that
the implementation can reencode Unicode-encoded legacy fonts.
-e specifies a directory with encoding files. Every such directory is scanned for encoding files, the list of which is then written to
an "encodings.dir" file in every font directory.
-p Specifies a prefix that is prepended to the encoding file path names when they are written to the "encodings.dir" file. The prefix
is prepended literally: if a `/' is required between the prefix and the path names, it must be supplied explicitly as part of the
prefix.
-r Keep non-absolute encoding directories in their relative form when writing the "encodings.dir" file. The default is to convert rel-
ative encoding directories to absolute directories by prepending the current directory. The positioning of this options is signifi-
cant, as this option only applies to subsequent -e options.
-n do not scan for fonts, do not write font directory files. This option is useful when generating encoding directories only.
-- end of options.
SEE ALSO
X(7), Xserver(1), mkfontdir(1), ttmkfdir(1), xfs(1), xset(1)
NOTES
The format of the fonts.scale, fonts.dir and encodings.dir files is documented in the mkfontdir(1) manual page.
Mkfontscale will overwrite any fonts.scale file even if it has been hand-edited.
mkfontscale -b -s -l is equivalent to mkfontdir.
AUTHOR
The version of mkfontscale included in this X.Org Foundation release was originally written by Juliusz Chroboczek <jch@freedesktop.org> for
the XFree86 project. The functionality of this program was inspired by the ttmkfdir utility by Joerg Pommnitz.
X Version 11 mkfontscale 1.0.6 MKFONTSCALE(1)