02-27-2006
with the original jfs, i think there was a limit of how many "PP"s you can have per physical volume... or something like that. with jfs2, i don't think there's limit that anyone would realistically reach for most applications. certainly, 1TB in this case could easily be attained.
8 More Discussions You Might Find Interesting
1. UNIX for Dummies Questions & Answers
1 . Thanks everyone who read the post first.
2 . I have a log file which size is 143M , I can not use vi open it .I can not use xedit open it too.
How to view it ?
If I want to view 200-300 ,how can I implement it
3 . Thanks (3 Replies)
Discussion started by: chenhao_no1
3 Replies
2. UNIX for Dummies Questions & Answers
Hi,
I am quite sure that I am posting a question in the very wrong forum but I have to give a try. It's a question about UNIX theory. I don't have any clue of how to solve this question. If someone could kindly provide some good references or give me the formulas, it will be really... (1 Reply)
Discussion started by: ti_ma
1 Replies
3. UNIX for Dummies Questions & Answers
The /src file is obviously designed to contain source code, so when I download programs, I should put them in /src (because they contain the source files + the executables)? What do most people do with the executables? Do they copy them to /bin, make links to them in /bin, or just leave them in... (4 Replies)
Discussion started by: css136
4 Replies
4. UNIX for Dummies Questions & Answers
I have a 5000 line config.log file with several "maybe" errors. Any reccomendations on finding solvable problems? (2 Replies)
Discussion started by: NeedLotsofHelp
2 Replies
5. Shell Programming and Scripting
Input file
DATA2.2 POSITION_152486.2 COLUMN689699.2
DATA2.2 ROW00000342066 UNIT00000342313
DATA7.2 POSITION_017891.4 COLUMN060361.4
DATA7.2 ROW00000379319 UNIT00000368623
DATA7.2 ROW00000421241 UNIT00000400736
DATA8.1 POSITION_153254.2 COLUMN694986.2
DATA8.1 ROW00000379288... (1 Reply)
Discussion started by: perl_beginner
1 Replies
6. UNIX for Dummies Questions & Answers
Does anyone have any idea of how I can make something like the code below run recursively?
I'll run it on a tree of directories all with different names and all containing a sequence of .dpx files. I've tried to do it using find and exec but can't get it to work right.
What it needs to do is... (4 Replies)
Discussion started by: scribling
4 Replies
7. What is on Your Mind?
Hello,
I have been working as Solaris/Linux Admin since past 8 years. I am looking options for my profile change, but there is some limitation. I worked as 24x7 support for admin, server support, high availability, etc. But been worked on developing side and scripting part.
When I search for Big... (2 Replies)
Discussion started by: nightup2222
2 Replies
8. Solaris
Gents
Actually I have question and i need your support.
I have this NAS file system mounted as /coresys has size of 7 TB
I need to Split this file system into several file systems as mount points I mean how to can I Split it professionally to different NAS mount points how to can I decide... (2 Replies)
Discussion started by: AbuAliiiiiiiiii
2 Replies
lvmpvg(4) Kernel Interfaces Manual lvmpvg(4)
NAME
lvmpvg - LVM physical volume group information file
SYNOPSIS
DESCRIPTION
is an ASCII file that stores the volume-group information for all of the physical volume groups in the system. The information is stored
in a hierarchical format.
First, it starts with a volume group under which multiple physical volume groups can exist. Under each physical volume group, a list of
physical volumes can be specified. There must be at least one physical volume group in each volume group that appears in this file. The
physical-volume-group name must be unique within the corresponding volume group, although it is permissible to use a common physical volume
group name across different volume groups. There can be as many volume groups in this file as there are in the system.
Instead of using the and commands, the administrator can edit this file to create and extend physical volume groups. However, care must be
taken to ensure that all physical volumes to be included in the file have already been defined in their respective volume groups by previ-
ous use of or
The file format has the following structure. and are keywords that introduce the names of the volume group and physical volume group,
respectively.
pv_path
...
pv_path
...
pv_path
...
The variables are defined as follows:
pv_path The block device path name of a physical volume within the volume group.
pvg_name The name of the physical volume group. It must be unique within the volume group.
vg_name The path name of the volume group.
EXAMPLES
The following example shows an file containing two volume groups: the first containing two physical volume groups, each with two physical
volumes defined in it; the second containing three physical volume groups, each with one physical volume defined in it.
SEE ALSO
vgcreate(1M), vgextend(1M), vgreduce(1M), vgremove(1M), intro(7), lvm(7).
lvmpvg(4)