9 More Discussions You Might Find Interesting
1. AIX
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
2. AIX
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
3. AIX
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
4. AIX
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
5. AIX
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
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
7. AIX
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
8. UNIX for Dummies Questions & Answers
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
9. UNIX for Advanced & Expert Users
Hi there,
Can anyone tell me the advantages that jfs has over Veritas (if any)??
Cheers. (5 Replies)
Discussion started by: rich
5 Replies
fsck.jfs(8) JFS utility - file system check fsck.jfs(8)
NAME
fsck.jfs - initiate replay of the JFS transaction log, and check and repair a JFS formatted device
SYNOPSIS
fsck.jfs [ -afnopvV ] device
DESCRIPTION
fsck.jfs is used to replay the JFS transaction log, check a JFS formatted device for errors, and fix any errors found.
device is the special file name corresponding to the actual device to be checked (e.g. /dev/hdb1).
fsck.jfs must be run as root.
WARNING
fsck.jfs should only be used to check an unmounted file system or a file system that is mounted READ ONLY. Using fsck.jfs to check a file
system mounted other than READ ONLY could seriously damage the file system!
OPTIONS
If no options are selected, the default is -p.
-a Autocheck mode - Replay the transaction log. Do not continue fsck processing unless the aggregate state is dirty or the log replay
failed. Functionally equivalent to -p. Autocheck mode is typically the default mode used when fsck.jfs is called at boot time.
-f Replay the transaction log and force checking even if the file system appears clean. Repair all problems automatically.
-n Open the file system read only. Do not replay the transaction log. Report errors, but do not repair them.
-o Omit the replay of the transaction log. This option should not be used unless as a last resort (i.e. the log has been severely
corrupted and replaying it causes further problems).
-p Automatically repair ("preen") the file system. Replay the transaction log. Do not continue fsck processing unless the aggregate
state is dirty or the log replay failed. Functionally equivalent to -a.
-v Verbose messaging - print details and debug statements to stdout.
-V Print version information and exit (regardless of any other chosen options).
EXAMPLES
Check the 3rd partition on the 2nd hard disk, print extended information to stdout, replay the transaction log, force complete fsck.jfs
checking, and give permission to repair all errors:
fsck.jfs -v -f /dev/hdb3
Check the 5th partition on the 1st hard disk, and report, but do not repair, any errors:
fsck.jfs -n /dev/hda5
EXIT CODE
The exit code returned by fsck.jfs represents one of the following conditions:
0 No errors
1 File system errors corrected and/or transaction log replayed successfully
2 File system errors corrected, system should be rebooted if file system was mounted
4 File system errors left uncorrected
8 Operational error
16 Usage or syntax error
128 Shared library error
REPORTING BUGS
If you find a bug in JFS or fsck.jfs, please report it via the bug tracking system ("Report Bugs" section) of the JFS project web site:
http://oss.software.ibm.com/jfs
Please send as much pertinent information as possible, including the complete output of running fsck.jfs with the -v option on the JFS
device.
SEE ALSO
fsck(8), mkfs.jfs(8), logdump(8), logredo(8), xchklog(8), xchkdmp(8), xpeek(8)
AUTHORS
Barry Arndt (barndt@us.ibm.com)
William Braswell, Jr.
fsck.jfs is maintained by IBM.
See the JFS project web site for more details:
http://oss.software.ibm.com/jfs
March 1, 2002 fsck.jfs(8)