Tek-Tips is the largest IT community on the Internet today!

Members share and learn making Tek-Tips Forums the best source of peer-reviewed technical information on the Internet!

  • Congratulations SkipVought on being selected by the Tek-Tips community for having the most helpful posts in the forums last week. Way to Go!

Can not extend a JFS file system with nbpi = 4096 1

Status
Not open for further replies.

zaurak

Technical User
Sep 6, 2002
10
0
0
PL
I can't extend filesystem
chfs -a size='+1000000' /oracle/PRD/sapdata3
I have error:
chfs: Can not extend a JFS file system with nbpi = 4096
and frag = 4096 past 134217728 (512 byte blocks)

below is specification
[Entry Fields]
File system name /oracle/PRD/sapdata3
NEW mount point [/oracle/PRD/sapdata3]
SIZE of file system (in 512-byte blocks) [134217728]
Mount GROUP []
Mount AUTOMATICALLY at system restart? no +
PERMISSIONS read/write +
Mount OPTIONS [] +
Start Disk Accounting? no +
Fragment Size (bytes) 4096
Number of bytes per inode 4096
Compression algorithm no
Large File Enabled false
Allocation Group Size (MBytes) 8

LOGICAL VOLUME: lvpsapdata3 VOLUME GROUP: prddata3
LV IDENTIFIER: 0041870a93db28b2.1 PERMISSION: read/write
VG STATE: active/complete LV STATE: opened/syncd
TYPE: jfs WRITE VERIFY: off
MAX LPs: 3048 PP SIZE: 32 megabyte(s)
COPIES: 2 SCHED POLICY: parallel
LPs: 2048 PPs: 4096
STALE PPs: 0 BB POLICY: relocatable
INTER-POLICY: maximum RELOCATABLE: yes
INTRA-POLICY: middle UPPER BOUND: 32
MOUNT POINT: /oracle/PRD/sapdata3 LABEL: /oracle/PRD/sapdata3
MIRROR WRITE CONSISTENCY: on
EACH LP COPY ON A SEPARATE PV ?: yes
 
Hi,
you have reached the maximum size this filesystem can grow to use nbi value of 4096

see man chfs , it shows you the list , following list from man chfs
nbpi Fragment size in bytes Maximum size in 512-byte blocks

4096 512, 1024, 2048, 4096 134217728

you will have to re-create the filesystem with a bigger nbpi and frag size , i don't think you can increase this value on the fly or by umounting filesystem & changing it

you probably have to backup data , rec-create FS and restore back data.

 
I use the following chart:

nbpi Fragment size in bytes Maximum size in 512-byte blocks
512 512, 1024, 2048, 4096 16777216
1024 512, 1024, 2048, 4096 33554432
2048 512, 1024, 2048, 4096 67108864
4096 512, 1024, 2048, 4096 134217728
8192 512, 1024, 2048, 4096 268435456
16384 512 268435456
16384 1024, 2048, 4096 536870912
32768 512 268435456
32768 1024 536870912
32768 2048, 4096 1073741824
65536, 131072 512 268435456
65536, 131072 1024 536870912
65536, 131072 2048 1073741824
65536, 131072 4096 2147483648
AIX Version 4.1 is limited to NBPI values from 512 to 16384.
In AIX Version 4.3, you can have NBPI values from 512 to 128K, with corresponding maximum file system sizes.
 
Hello,
I just ran across this same problem (hense the reason for reading this thread). I have a couple questions, what are the affects of increasing/decreasing "Fragment Size" and "Number of bytes per inode"? Also, how is the ceiling calculated? If I increase NBI to 8K or 16K, what will my new FS max size be?

Maybe I should have started a new thread, but I thought the questions were appropriate for this one as well.

Thanks,
Tim
 
Hello,
You have things mirrored.

Before the increase of jfs file system do the below listed step.
look at lsvg vgname
lsvg -p vgname to see how many free pp's availabel.
make sure the mirror copies are not stale.
If you do not have free pp's to extend file system then you are going to get error.
 
Status
Not open for further replies.

Part and Inventory Search

Sponsor

Back
Top