06-06-2005
Since the threadstarter hasn't provided any data that could shed any light on his problem I'm jsut left to guesses.
Having said this: There are some limitations in jfs which may cause the problem: "Number of Bytes per Inode" and "Allocation Group Size" for instance. In this case the only thing you can do is to back up the FS, drop/recreate it with different values and restore the data.
bakunin
10 More Discussions You Might Find Interesting
1. UNIX for Advanced & Expert Users
Now, i know a ufs file system can be increased using mkfs but hwo do I take space from a file system and add it to another file system? at my job here, that seems to be possible because I see request on it almost every day.
what is the exact command to do this and does the system need to be... (1 Reply)
Discussion started by: TRUEST
1 Replies
2. UNIX for Dummies Questions & Answers
Hello all
Can someone tell me I am running a script and the outputs directory is too small to contain the newly created file as a result of this script. How can I increase the directory size?
Thanks (9 Replies)
Discussion started by: jonest
9 Replies
3. HP-UX
Hi Experts,
I am not sure whether my question should be in this thread or some other one. I am using HP Tru64 system.
Currently one of my filesystem /others is almost full. I need to know the exact commands to increase this filesystem. Please show me how to check for free partitions and add... (5 Replies)
Discussion started by: kingsto88
5 Replies
4. HP-UX
We increased our server's RAM 8 -> 32 GB RAM. swap memory is currently 10 GB. With which command I can increase this memory? (1 Reply)
Discussion started by: akyuceisik
1 Replies
5. AIX
hi
Im using AIX4.3. Through smit I tried to increase the size of a directory. I changed 10,000 blocks more but finally i got 524288 blocks more. That is
before change : 12582912 blocks
I have tried for change: 12592912 blocks
then i execute smit.
But finally I got: ... (3 Replies)
Discussion started by: sumanbangladesh
3 Replies
6. AIX
Hello,
Does HACMP have bugs ? I have version 5.4 on AIX 6.1 and when I try to increase filesystem space or logical volume partitions which are under HACMP VG it gives me error:
# lsvg
rootvg
pr0oravg
px0oravg
pb0oravg
pr0sapvg
px0sapvg
pb0sapvg
pr1_pr2_vg
pr2_px1_vg
#
#... (11 Replies)
Discussion started by: filosophizer
11 Replies
7. AIX
Hi guys,
I want to increase my ./usr or just one path in my aix6.1 machine.
currently if I
# lsvg rootvg
VOLUME GROUP: rootvg VG IDENTIFIER: 00f6126500004c00000 0012aef0c9035
VG STATE: active PP SIZE: 128... (2 Replies)
Discussion started by: pilotHans
2 Replies
8. Solaris
Hi All,
I have got a RAID 5 SVM in my Solaris Box. Recently we had performance issues with it. So SUN has told us to increase the interlace size to 128k.
how can we do it so that we have to recreate the RAID 5. ALso guide what are all the pre cautions that we need to take before doing... (1 Reply)
Discussion started by: jegaraman
1 Replies
9. AIX
Hi Friends,
I have a problem while increasing the fileystem. Actually the filesystem is 256 gb
and i have to add another 256 gb.So i got a new lun(hdisk) with 256 gb.
I added to the vg using the extendvg command.
It was successfully added, and when i checked the free pp's in vg it was showing... (4 Replies)
Discussion started by: Mohamed Thamim
4 Replies
10. Hardware
Hi Guys
We have a VM machine, now I want to increase the size of the filesystem.
We are running RHEL6 O/S.
I have filesystem that is 500GB I want to increase that filesystem to 1.5 TB.
The guy who manages the VM increased the size on the VM machine, now how do I make sure that the... (7 Replies)
Discussion started by: Phuti
7 Replies
LEARN ABOUT REDHAT
fsck.jfs
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)