[Search for users] [Overall Top Noters] [List of all Conferences] [Download this site]

Conference turris::digital_unix

Title:	DIGITAL UNIX(FORMERLY KNOWN AS DEC OSF/1)
Notice:	Welcome to the Digital UNIX Conference
Moderator:	SMURF::DENHAM

Created:	Thu Mar 16 1995
Last Modified:	Fri Jun 06 1997
Last Successful Update:	Fri Jun 06 1997
Number of topics:	10068
Total number of notes:	35879

9517.0. "fsck failure" by ZPOVC::TOOSENG () Wed Apr 16 1997 08:08

    We have a customer with the following problem (they are running
    Digital Unix 3.2G on an AlphaServer 4100):
    
    
    1. After power up the machine, the following messages appeared:
    
       /dev/rre1g: MISSING '..' I=2 OWNER=SAG MODE=40755
       /dev/rre1g: SIZE=512 MTIME=DEC 31 08:38 1996
       /dev/rre1g: DIR=?
       /dev/rre1g: UNEXPECTED INCONSISTENCY; RUN fsck MANUALLY
       INIT: SINGLE-USER MODE
       #
    
    2. At the # prompt, we type fsck
    
       #fsck /dev/rre1g
       ...
       CANNOT FIX, SECOND ENTRY IN DIRECTORY CONTAINS lost+found
       ...
       *** Phase 3
       UNREF DIR I=20 OWNER=root MODE=41777
       SIZE=66560 MTIME=Feb 18 17:42 1997
       RECONNECT? [yn] n
       UNREF DIR i=20 OWNER=root MODE=41777
       SIZE=66560 MTIME=Feb 18 17:42 1997
       RECONNECT? [yn] n
       ...
       filesystem still has errors - rerun fsck
       #
    
    3. At this point, we type fsck -y
    
       ...
       RECONNECT? [yn] yes
       SORRY, No lost+found DIRECTORY
       *** Phase 4
       ...
       ADJUST: yes
       ...
       filesystem still has errors - rerun fsck
    
    
    
    We have rerun fsck a number of times. No luck. Any suggestion?
    
    Thanks.
    
    
    
    Regards,
    
    Too-Seng

T.R Title User Personal
Name Date Lines

9517.1 NABETH::alan Dr. File System's Home for Wayward Inodes. Wed Apr 16 1997 13:02 15

T.R	Title	User	Personal Name	Date	Lines
9517.1		NABETH::alan	Dr. File System's Home for Wayward Inodes.	`Wed Apr 16 1997 13:02`	15
	They have a very corrupt file system. The first two entries of a directory are supposed to be "." and ".."; the current directory and the parent directory. At the root of a file system these are the same inode.� From the 2nd message it appears that the file system is finding the lost+found directory as the 2nd entry, instead of "..". In the 3rd, when it goes to create the lost+found directory, it fails. You might want to make a physical backup of the file system and ship off a copy of it with an IMPT case to see there is something that can be done to fsck to make it handle this particular problem. Then, recreate the file system and restore from the last backup. You might also want to look through the error log to see if there I/O error that would explain the corruption.

	They have a very corrupt file system.  The first two entries
	of a directory are supposed to be "." and ".."; the current
	directory and the parent directory.  At the root of a file
	system these are the same inode.� From the 2nd message it
	appears that the file system is finding the lost+found directory
	as the 2nd entry, instead of "..".  In the 3rd, when it goes
	to create the lost+found directory, it fails.

	You might want to make a physical backup of the file system
	and ship off a copy of it with an IMPT case to see there is
	something that can be done to fsck to make it handle this
	particular problem.  Then, recreate the file system and
	restore from the last backup.  You might also want to look
	through the error log to see if there I/O error that would
	explain the corruption.