09-06-2010
if fsck output contains only two types of errors as listed below, then probably all data blocks are intact and there is no data loss. but we'll need to have a look at the entire fsck output to be sure.
error type 1 : Directory entry ... is not an allocated inode
error type 2 : File inode 1191665 is not referenced by any directory
we need to check if these errors are related to each other. if they are, then all the inodes moved to lost+found are those whose directory entries were removed by fsck. in this case, you could check the contents of lost+found and if you could identify the entries in it, they could be restored.
in the meanwhile, i'm checking if the fsck expert person (about gpfs) could see this and tell us more.
edit : i checked with fsck expert who is working with gpfs and he confirmed that there should be no data loss (as stated above), and the detached entries should be available in lost+found which could be used for corrections.
Last edited by Yogesh Sawant; 09-06-2010 at 04:01 AM..
10 More Discussions You Might Find Interesting
1. Solaris
Hi All,
I am working with the Solaris 9.
In df -h command / file system size is 9.6 GB , used 7.5 GB and avialble space is 2.1. OK
But in du -hd command it is showing some 4.1 GB only.
How to find out that remaining 3.4GB.
Can you please help me ...
Thanks and Regards, (1 Reply)
Discussion started by: lbreddy
1 Replies
2. Solaris
Hi,
In df -h root file system showing
(total size) (used) (free)
/dev/dsk/c0t0d0s0 11G 7.6G 2.8G 73% /
but du -hd command showng 5.1 gb used sapce.
I am missing 3.00 gb space.
Here I have to knoe where is Remaining space... (2 Replies)
Discussion started by: lbreddy
2 Replies
3. Solaris
Hi All,
This is Babu working as a system administrator.
Here I am getting one problem with one of my Sun server's root (/) file system.
In df -h command / file system showing 7.8 GB used space.But in du -hd command it showing 5.2 gb only.
Please can any one help me resolve this issue... (2 Replies)
Discussion started by: lbreddy
2 Replies
4. AIX
Unix people..
Backup for GPFS file system
/dev/gpfs /application
I have GPFS file system and I'd like to take backup for that file system to the tape
I'm using this command Smitty fs + Backup a File System
And I'm take the backup but this is will work if that gfs2 but I'm... (4 Replies)
Discussion started by: Mr.AIX
4 Replies
5. Solaris
Hi
I would like to know one thing while recovering from corrupt /etc/system file.
For that we have to do at ok> boot -a
when system ask for system file we give /dev/null. Could any one tell me what /dev/null value will do in this case.
Regards (1 Reply)
Discussion started by: sb200
1 Replies
6. AIX
dear all
can i create two gpfs in one node each gpfs is pointing to single hdiskpower (1 Reply)
Discussion started by: thecobra151
1 Replies
7. AIX
Hi,
I have a running GPFS cluster. For one every mountpoint that i have created i have one disk assigned to it. That disk is converted to an NSD and is a part of the GPFS Cluster.
Now i have a new disk and there is this requirement to add it to the GPFS cluster, such that this becomes an NSD.... (1 Reply)
Discussion started by: aixromeo
1 Replies
8. Shell Programming and Scripting
I have a C++ binary executable installed in a file system which is shared across multiple solaris boxes.
When I start this executable from one of the boxes,I am able to start only 4 parallel instances and from the 5th instance onwards I am getting the following error.
fatal: libdb2.so.1:... (2 Replies)
Discussion started by: prasperl
2 Replies
9. Red Hat
Hi gurus,
Need your help ,
Am facing some issue with one of the ext3 file system.while rebooting it failed to mount fs after running fsck i tried manuall but still no luck.However i made the machine up but am unable to mount file system can some one please help me.
root@vm258902]~# cat... (2 Replies)
Discussion started by: kapil514
2 Replies
10. AIX
Hi Everyone
I have configured two node GPFS cluster and it is running fine. But today when I have rebooted one of the node and after starting GPFS one node shows down. on investigating I have checked that mmfsNodeData file is missing from location /var/mmfs/gen/ on one node. I am receiving the... (1 Reply)
Discussion started by: m_raheelahmed
1 Replies
LEARN ABOUT HPUX
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