Sponsored Content
Full Discussion: Jfs and jfs2
Operating Systems AIX Jfs and jfs2 Post 302360789 by nagchundu on Saturday 10th of October 2009 10:30:48 AM
Old 10-10-2009
in jfs number of inodes are fixed,in jfs2 dynamically inodes are generated
jfs inode size will be max 128 bytes ,in jfs2 max size is 512 bytes
jfs have only one log file but jfs2 every FS can have own log file
log file is observe the process in file system
 

9 More Discussions You Might Find Interesting

1. UNIX for Advanced & Expert Users

jfs (jfs2) for AIX versus Veritas

Hi there, Can anyone tell me the advantages that jfs has over Veritas (if any)?? Cheers. (5 Replies)
Discussion started by: rich
5 Replies

2. UNIX for Dummies Questions & Answers

creating jfs

Need help, I have read the docs but need some better understanding. Can someone explain the reasons behind setting the values for fragement size, i-node and allocation group size? Thanks, (6 Replies)
Discussion started by: kburrows
6 Replies

3. AIX

Can not extend a JFS file system

Hi, I am getting an error message when i try to increase the size of a filesystems under AIX 4.3.3: chfs: 0506-932 Can not extend a JFS file system with nbpi = 4096 and frag = 4096 past 134217728 (512 byte blocks). -> Characteristics Journaled File System ... (4 Replies)
Discussion started by: Can
4 Replies

4. AIX

JFS and JFS2

hi all, can sumbody give me a link which gives the basic layout of JFS, JFS2 and the veritas file system. and i also want to know about the data structures used in this filsystem thanx in advance (0 Replies)
Discussion started by: anwerreyaz
0 Replies

5. AIX

160G SAN FS on JFS

Hi All, I can't create a FS from a SAN VG with size of 160G on JFS (NOT JFS2, requirement with application) with large file enabled. It only let me create 64G in maximum size. The actual size of SAN VG is also 160G, the FS can be smaller than 160G because of the inode allocation. Please... (1 Reply)
Discussion started by: itik
1 Replies

6. AIX

jfs2 - cannot shrink filesystem

Hi, is anyone aware about filesystem size restrictions on AIX? And does anyone know a solution for below problem? I have 2 boxes attached to EMC Raid5 storage, both have huge /optware/oracle/oradata filesystems - 4.5 and 2.5 TB in size, nothing is striped or in any other way restricted. Due to... (11 Replies)
Discussion started by: zxmaus
11 Replies

7. AIX

Cannot grow jfs file system on AIX 5.2

Hello all, I'm trying to grow a file system by 500MB using SMIT on AIX 5.2 but I receive this error: "0516-404 allocp: This system cannot fulfill the allocation request. There are not enough free partitions or not enough physical volumes to keep strictness and satisfy allocation requests.... (3 Replies)
Discussion started by: need2bageek
3 Replies

8. AIX

Help with jfs

how to change the filesystem from jfs to jfs2 in ibm aix6.1 please tell me command for that. thank you, paandu (2 Replies)
Discussion started by: paandur
2 Replies

9. AIX

AIX JFS2 content

Hello! I have a LPAR with 51GB RAM topas shows 21% of memory for client pages (~11Gb) svmon -G show 2906772 client pages in use (~11Gb) but then i try to investigate per process client memory usage svmon -P -O filtertype=client and summarize inuse column, i get only 347880 pages... (1 Reply)
Discussion started by: sys
1 Replies
jfs_fscklog(8)						   Extract/Display JFS fsck Log 					    jfs_fscklog(8)

NAME
jfs_fscklog - extract a JFS fsck service log into a file and/or format and display the extracted file SYNOPSIS
jfs_fscklog [ -d ] [ -e device ] [ -f output.file ] [ -p ] [ -V ] DESCRIPTION
jfs_fscklog with option -e device extracts the contents of either the most recent or immediately prior (specified with option -p) JFS fsck service log from the specified device, and writes the output to a file. The file name may be specified with the -f option, or the default file name is <pwd>fscklog.new. If the -p option is used, the default file name is <pwd>fscklog.old. jfs_fscklog with option -d formats and displays the contents of the extracted file. jfs_fscklog with options -d and -e device extracts and displays the JFS fsck service log. OPTIONS
-d Format and display a previously extracted JFS fsck service log. -e device Extract the JFS fsck service log from device and store it in a file. (device is the special file name corresponding to the actual device from which the fsck log will be extracted (e.g. /dev/hdb1 )). -f file.name Specify the file name, overriding the default file name. When used with -e device, file.name specifies the name of the file into which the JFS fsck log will be extracted. When used with -d, file.name specifies the name of the extracted file whose contents will be formatted and displayed. file.name must be 127 characters or less in length. file.name will be created in the present working directory unless it is fully qualified. -p Extract the prior log (as opposed to the most recent log). -V Print version information and exit (regardless of any other chosen options). EXAMPLES
Extract the most recent JFS fsck log on /dev/hda5 into <pwd>fscklog.new: jfs_fscklog -e /dev/hda5 Extract the most recent JFS fsck log on /dev/hdb3 into /temp/l9651107.log: jfs_fscklog -e /dev/hdb3 -f /temp/l9651107.log Display the JFS fsck log that was extracted into /temp/l9651107.log: jfs_fscklog -d -f /temp/l9651107.log Extract and display the previous JFS fsck log from /dev/hda8: jfs_fscklog -e /dev/hda8 -d -p REPORTING BUGS
If you find a bug in JFS or jfs_fscklog, please report it via the bug tracking system ("Report Bugs" section) of the JFS project web site: http://jfs.sourceforge.net/ Please send as much pertinent information as possible, including any jfs_fscklog error messages and the complete output of running jfs_fsck with the -v option on the JFS device. SEE ALSO
jfs_fsck(8), jfs_mkfs(8), jfs_tune(8), jfs_logdump(8), jfs_debugfs(8) AUTHOR
Barry Arndt (barndt@us.ibm.com) jfs_fscklog is maintained by IBM. See the JFS project web site for more details: http://jfs.sourceforge.net/ October 28, 2002 jfs_fscklog(8)
All times are GMT -4. The time now is 10:08 AM.
Unix & Linux Forums Content Copyright 1993-2022. All Rights Reserved.
Privacy Policy