Sponsored Content
Operating Systems Solaris / root is 100% and there is nothing increased it Post 302459182 by jlliagre on Monday 4th of October 2010 03:37:45 AM
Old 10-04-2010
Quote:
Originally Posted by DGPickett
If you have the open deleted files in a /lost+found dir
You are confusing things. The lost+found directory is designed to contain files that have been disconnected from the file system after some operating system dysfunction like a power failure. By convention, they are relocated by fsck under the lost+found directory in their file system root. This is unrelated with unlinked files which are no more on the file system but still use disk space. The latter can be easily detected by looking for regular files with 0 links under /proc/<pid>/fd/*.
 

4 More Discussions You Might Find Interesting

1. Red Hat

how to mount SAN volume with its increased size

Hi, We have 200GB SAN volume mounted on Redhat EL 5. which is working fine. As my SAN supports dynamic resizing of volumes, i unmounted the volume and resized the SAN Volume to 300 GB successfully. Then i mounted again but it shows 200GB only but data is intact. Now, my requirement is to let... (3 Replies)
Discussion started by: prvnrk
3 Replies

2. AIX

rmt0 allows get increased .. !

rmt0 allows get increased .. ! I have faced this issue in my AIX server, rmt0 allows get increased and it's filled /root till 100% There is no tape in tape drive why it's increased? Pls advice.. (1 Reply)
Discussion started by: Mr.AIX
1 Replies

3. Solaris

Migration of system having UFS root FS with zones root to ZFS root FS

Hi All After downloading ZFS documentation from oracle site, I am able to successfully migrate UFS root FS without zones to ZFS root FS. But in case of UFS root file system with zones , I am successfully able to migrate global zone to zfs root file system but zone are still in UFS root file... (2 Replies)
Discussion started by: sb200
2 Replies

4. Shell Programming and Scripting

How can I get the increased rate in MB?

Deal all, I have a directory called I want to know how many MBs are transferred to it every 2 hours. How can I do this? Any ideas? I have a simple idea but I can't translate it into shell script, the idea is: 1- get the size of the folder now, using 2- then get the size of the... (4 Replies)
Discussion started by: Mohannad
4 Replies
FSCK_HFS(8)						    BSD System Manager's Manual 					       FSCK_HFS(8)

NAME
fsck.hfs -- HFS file system consistency check SYNOPSIS
fsck.hfs -q [-df] special ... fsck.hfs -p [-df] special ... fsck.hfs [-n | -y | -r] [-dfgl] [-m mode] [-c size] special ... DESCRIPTION
The fsck.hfs utility verifies and repairs standard HFS and HFS+ file systems. The first form of fsck.hfs quickly checks the specified file systems to determine whether they were cleanly unmounted. The second form of fsck.hfs preens the specified file systems. It is normally started by fsck(8) during systen boot, when a HFS file system is detected. When preening file systems, fsck.hfs will fix common inconsistencies for file systems that were not unmounted cleanly. If more serious problems are found, fsck.hfs does not try to fix them, indicates that it was not successful, and exits. The third form of fsck.hfs checks the specified file systems and tries to repair all detected inconsistencies. If no options are specified fsck.hfs will always check and attempt to fix the specified file systems. The options are as follows: -c size Specify the size of the cache used by fsck.hfs internally. Bigger size can result in better performance but can result in deadlock when used with -l option. Size can be specified as a decimal, octal, or hexadecimal number. If the number ends with a ``k'', ``m'', or ``g'', the number is multiplied by 1024 (1K), 1048576 (1M), or 1073741824 (1G), respectively. -d Display debugging information. This option may provide useful information when fsck.hfs cannot repair a damaged file system. -f When used with the -p option, force fsck.hfs to check `clean' file systems, otherwise it means force fsck.hfs to check and repair journaled HFS+ file systems. -g Causes fsck.hfs to generate its output strings in GUI format. This option is used when another application with a graphical user interface (like Mac OS X Disk Utility) is invoking the fsck.hfs tool. -l Lock down the file system and perform a test-only check. This makes it possible to check a file system that is currently mounted, although no repairs can be made. -m mode Mode is an octal number that will be used to set the permissions for the lost+found directory when it is created. The lost+found directory is only created when a volume is repaired and orphaned files or directories are detected. fsck.hfs places orphaned files and directories into the lost+found directory (located at the root of the volume). The default mode is 01777. -p Preen the specified file systems. -q Causes fsck.hfs to quickly check whether the volume was unmounted cleanly. If the volume was unmounted cleanly, then the exit status is 0. If the volume was not unmounted cleanly, then the exit status will be non-zero. In either case, a message is printed to standard output describing whether the volume was clean or dirty. -y Always attempt to repair any damage that is found. -n Never attempt to repair any damage that is found. -r Rebuild the catalog file on the specified file system. This option currently will only work if there is enough contiguous space on the specified file system for a new catalog file and if there is no damage to the leaf nodes in the existing catalog file. SEE ALSO
fsck(8) BUGS
fsck.hfs is not able to fix some inconsistencies that it detects. HISTORY
The fsck.hfs command appeared in Mac OS X Server 1.0 . Mac OS X November 21, 2002 Mac OS X
All times are GMT -4. The time now is 02:19 AM.
Unix & Linux Forums Content Copyright 1993-2022. All Rights Reserved.
Privacy Policy