Sponsored Content
Operating Systems Solaris Filesystem filling up and no clue as to why! Post 302238317 by zombiezparadize on Friday 19th of September 2008 03:02:47 PM
Old 09-19-2008
Filesystem filling up and no clue as to why!

df shows that the filesystem is filling up and the usage is 94%.
However when I actually traverse to the directory I du shows only about
10% of the space occupied!

Below is the output of df and du:
>>>df -kh
/cbmdata/00 470M 393M 29M 94% /cbmdata/00

>>>/cbmdata/00> du -sh *
57K billing
1K config
48M coreEMS
1.7M data
115K gdd
8K lost+found
4K sba

I am wondering how the hell is filesystem is so full!
Any pointers of what to look for and how would be a great help!

Thanks a lot.
 

4 More Discussions You Might Find Interesting

1. Programming

I have no clue what's the point - fcntl() ?

hi, I need to know how to lock a file. I used the following code, but after executing the program the file 'write.txt' remined empty, and I have no idea why.Maybe I'm not using the corresponding syntax for blocking a file. But I deleted then the blocking part and the problem persisted. see to... (2 Replies)
Discussion started by: atticus
2 Replies

2. UNIX for Advanced & Expert Users

diff command filling /var filesystem space

Hi, I am using diff command to check difference between two files.Both files are very big and when i execute this command /var temp space is filled up almost 99%. Can any one please tell me is there any way i can specify directory name which has more space so that diff can use that dir for... (2 Replies)
Discussion started by: ukatru
2 Replies

3. UNIX for Dummies Questions & Answers

Root filesystem filling up!

Hi all. New to the forum and new to Unix admin... / filesystem filled up and I can't find where the large files are. Any help will be apppreciated: # df -k Filesystem kbytes used avail capacity Mounted on /dev/dsk/c1t0d0s0 8063580 7941745 41200 100% / /proc ... (4 Replies)
Discussion started by: jamie_collins
4 Replies

4. Shell Programming and Scripting

Need a clue to write a IF statement

Hi all, i am writing a shell script in which i got stuck when tried to use a if statement. This is my code : #!/bin/sh today=`date +"%a %b %e"` find /prod/logs -name '*.log' -mtime 0 -exec cp {} /home/hzjnr0/test \; find /home/hzjnr0/test -type f -exec grep -i "successfully" {} \; >... (6 Replies)
Discussion started by: Soma Das
6 Replies
gfs_jadd(8)						      System Manager's Manual						       gfs_jadd(8)

NAME
gfs_jadd - Add journals to a GFS filesystem SYNOPSIS
gfs_jadd [OPTION]... <DEVICE|MOINTPOINT>... DESCRIPTION
gfs_jadd is used to add journals to a GFS filesystem after the device upon which the filesystem resides has been grown. By running gfs_jadd on a GFS filesystem, you are filling in space between the current end of the filesystem and the end of the device upon which the filesystem resides. When this operation is complete, the journal index is updated so that machines mounting the filesystem at a later date will see the newly created journals in addition to the journals already there. Machines which are already running in the cluster are unaf- fected. gfs_jadd will not use space that has been formatted for filesystem data even if that space has never been populated with files. You may only run gfs_jadd on a mounted filesystem, addition of journals to unmounted filesystems is not supported. You only need to run gfs_jadd on one node in the cluster. All the other nodes will see the expansion has occurred when required. You must be superuser to execute gfs_jadd. The gfs_jadd tool tries to prevent you from corrupting your filesystem by checking as many of the likely problems as it can. When growing a filesystem, only the last step of updating the journal index affects the currently mounted filesystem and so failure part way through the expansion process should leave your filesystem in its original state. You can run gfs_jadd with the -Tv flags to get a display of the current state of a mounted GFS filesystem. This can be useful to do after the journal addition process to see if the changes have been successful. OPTIONS
-j num The number of new journals to add. This defaults to 1. -J size The size of the new journals in megabytes. The defaults to 128MB (the minimum size allowed is 32MB). If you want to add journals of different sizes to the filesystem, you'll need to run gfs_jadd once for each different size of journal. The size you specify here will be rounded down so that it is a multiple of the journal segment size which was specified at filesystem creation time. -h Help. Prints out a short usage message and exits. -q Quiet. Turns down the verbosity level. -T Test. Do all calculations, but do not write any data to the disk and do not add journals. This is used to discover what the tool would have done were it run without this flag. You probably want to turn the verbosity level up in order to gain most information from this option. -V Version. Print version information, then exit. -v Verbose. Turn up verbosity of messages. SEE ALSO
mkfs.gfs(8) gfs_grow(8) gfs_jadd(8)
All times are GMT -4. The time now is 09:36 AM.
Unix & Linux Forums Content Copyright 1993-2022. All Rights Reserved.
Privacy Policy