OS/2, eCS & ArcaOS - Technical > Storage
JFS TRAP000E during unzip on JFS partition (same unzip on fat32 is ok)
Dariusz Piatkowski:
--- Quote from: Remy on December 05, 2022, 03:53:36 pm ---Same location.
Interesting, I use default AN size
What are you cache / buffer sizes ?
--- End quote ---
I have a bit of a different setup here, that being:
- CACHE = 1G
- MIN_BUFFER = 8000
- MAX_BUFFER = 16000
- SYNC_TIME = 32
- MAX_AGE = 128
- BUFFER_IDLE = 8
My machine is powered by a UPS, so unless something catastrophic actually happens I can afford the long sync time and max age setups. The machine uses SSDs here (Samsung 850 & 860 Evo) but still limitted by the SATA3 interface, so FS cache certainly helps.
From a personal 'interested in this stuff' perspective I have been testing different MIN & MAX buffer configs and found this 8k<=>16K to be a sweet spot for my use. Basically, regular 15-20 day uptimes of standard heavy web use, email, and occasional DEV work with a good balance of JFS's nfreecbufs and slrun<slruN while attempting to keep jbufs_protected as high as I can.
Doug Bissett:
--- Quote ---Any idea about this hung / TRAP000E ?
--- End quote ---
Just a WAG, but try turning off Lazy Write (cachejfs /LW:OFF at a command prompt.).
Remy:
Changing cache size or whatelse didn't prevent the trap except deleting files...
I could read that JFS has a fixed number of i-nodes
May it be possible i reached this maximum value ?
How to check i-nodes ?
Dave Yeo:
Hi Remy, I think you are confusing JFS with JFS2. JFS was AIX's file system and had a fixed number of inodes. JFS2 was a rewrite of JFS, first for OS/2, then ported to Linux and AIX and has a dynamic number of inodes.
You can use the stat command or ls -i
--- Code: ---H:\>stat h:/
File: h:/
Size: 0 Blocks: 0 IO Block: 49152 directory
Device: 5648h/22088d Inode: 8778591906650128431 Links: 1
Access: (0777/drwxrwxrwx) Uid: ( 0/ root) Gid: ( 0/ root)
Access: 2022-12-11 21:56:36.000000000 -0800
Modify: 2022-12-11 17:07:30.000000000 -0800
Change: 2022-12-11 17:07:30.000000000 -0800
Birth: 2022-12-11 21:56:36.000000000 -0800
H:\>ls -i h:/
9872134062851590269 jfs.part 1282181188518208385 mozilla
3386936443230352367 mm 773427466165056712 tmp
H:\>stat k:/
File: k:/
Size: 0 Blocks: 8 IO Block: 49152 directory
Device: 564bh/22091d Inode: 8778591906650128431 Links: 1
Access: (0777/drwxrwxrwx) Uid: ( 0/ root) Gid: ( 0/ root)
Access: 2022-04-05 04:02:40.000000000 -0700
Modify: 2022-11-19 21:23:18.000000000 -0800
Change: 2022-11-19 21:23:18.000000000 -0800
Birth: 2021-08-11 18:48:36.000000000 -0700
--- End code ---
H: is my 12GB JFS ram disk, K: is 300GB JFS partition. I'm not totally sure that these commands work correctly on OS/2. Need to test on Linux
I've used enough inodes, lots of small files, that chkdsk would fail due to OOM (out of memory), no crash.
Remy:
--- Quote from: Dave Yeo on December 12, 2022, 03:07:31 am ---Hi Remy, I think you are confusing JFS with JFS2. JFS was AIX's file system and had a fixed number of inodes. JFS2 was a rewrite of JFS, first for OS/2, then ported to Linux and AIX and has a dynamic number of inodes.
You can use the stat command or ls -i
--- Code: ---H:\>stat h:/
File: h:/
Size: 0 Blocks: 0 IO Block: 49152 directory
Device: 5648h/22088d Inode: 8778591906650128431 Links: 1
Access: (0777/drwxrwxrwx) Uid: ( 0/ root) Gid: ( 0/ root)
Access: 2022-12-11 21:56:36.000000000 -0800
Modify: 2022-12-11 17:07:30.000000000 -0800
Change: 2022-12-11 17:07:30.000000000 -0800
Birth: 2022-12-11 21:56:36.000000000 -0800
H:\>ls -i h:/
9872134062851590269 jfs.part 1282181188518208385 mozilla
3386936443230352367 mm 773427466165056712 tmp
H:\>stat k:/
File: k:/
Size: 0 Blocks: 8 IO Block: 49152 directory
Device: 564bh/22091d Inode: 8778591906650128431 Links: 1
Access: (0777/drwxrwxrwx) Uid: ( 0/ root) Gid: ( 0/ root)
Access: 2022-04-05 04:02:40.000000000 -0700
Modify: 2022-11-19 21:23:18.000000000 -0800
Change: 2022-11-19 21:23:18.000000000 -0800
Birth: 2021-08-11 18:48:36.000000000 -0700
--- End code ---
H: is my 12GB JFS ram disk, K: is 300GB JFS partition. I'm not totally sure that these commands work correctly on OS/2. Need to test on Linux
I've used enough inodes, lots of small files, that chkdsk would fail due to OOM (out of memory), no crash.
--- End quote ---
Thanks Dave, I'll check results on my side
Note:
I read under ecomstation that i-nodes have a fixed number set at initial time and if exausted, no more files can be writren despite frees space under the partition exist.
Navigation
[0] Message Index
[#] Next page
[*] Previous page
Go to full version