here in one of the server the lvol4 is having 20G and used space is 181M
but it showing 98% used kindly advice any one can i run fsck -y after unmounted that lvol4
Last edited by venikathir; 11-24-2011 at 08:54 AM..
Reason: Solved
Hi, it seems I've got an hw error on more than one device.
I use an AIX 5.2.
this is the problem desc.
Description
DISK OPERATION ERROR
Probable Causes
DASD DEVICE
Failure Causes
DISK DRIVE
DISK DRIVE ELECTRONICS
I wish to read the SYSLOG file, where is it ?
tk (1 Reply)
Hello everyone,
I was trying to install db2 on Ubuntu, but got messed up with manual installation and Synaptic. At the moment, I find myself with a filesystem where DB2 is NOT installed ( I removed it with a sudo rm :o ) and with Synaptic still flagging db2exc as installed. The problem is that... (1 Reply)
I have this in my .profile:
stty erase `tput kbs`
which sets erase to ^H for a vt and ^? for an xterm.
This has been fine up until now on all systems whether I login using a vt terminal emulator or an xterm.
On this new system though, if I log in directly using an xterm, backspace doesn't... (1 Reply)
:mad:
Dear All,
Here I am sending the error msg that come to to the terminal when I attempt to start my
linux redhat 2.4.18-3 system.
cheking file system
/boot clean
/home : clean
/usr :containing file system with errors,check forced
error reading block 35924(attempt to... (3 Replies)
May God never give you the bane of working on Solaris.
Now, I am trying to run this simple shell script:
#!/bin/sh
input="a
b
c"
data="123"
while read eachline
do
data="$data$eachline"
done << EOF
$(echo "$input")
EOF... (2 Replies)
I am seeing a strange behavior of the 'find' command on AIX. As you can see,
the find command sometimes finds the file and sometimes does not based on how
many characters I specified between the wildcards.
I know all of these issues
can be resolved by using double quotes like "*est*". But I... (3 Replies)
Hi,
I have a passwd file with 3 users belonging to the the root group (gid=0), but the group file does not list these users as members of the root group?
Shoud I be worried and apart from manually changing it, how can it be remediated?
thx
Norgaard (1 Reply)
We have a Sun Server running Solaris 10 and Veritas Cluster Server. The RAID Volumes in the Server (/ , swap, opt, var, usr) are managed by VxVm and UFS is grown on all these volumes.
Lately the system has been crashing due to an inconsistency in the opt filesystem. Upon reboot we did a fsck on... (1 Reply)
Hi All,
I am running a parallel processing on aggregating a file. I am splitting the process into 7 separate parallel process and processing the same input file and the process will do the same for each 7 run. The issue I am having is for some reason the 1st parallel processes complete first... (7 Replies)
Discussion started by: arunkumar_mca
7 Replies
LEARN ABOUT X11R4
fsck.hfsplus
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