Bug 4038

Summary: Wrong error msg, booting hosed file system
Product: [Retired] Red Hat Linux Reporter: bolotine
Component: filesystemAssignee: David Lawrence <dkl>
Status: CLOSED WONTFIX QA Contact:
Severity: medium Docs Contact:
Priority: medium    
Version: 5.2   
Target Milestone: ---   
Target Release: ---   
Hardware: i386   
OS: Linux   
Fixed In Version: Doc Type: Bug Fix
Doc Text:
Story Points: ---
Clone Of: Environment:
Last Closed: 1999-07-15 16:42:00 UTC Type: ---
Regression: --- Mount Type: ---
Documentation: --- CRM:
Verified Versions: Category: ---
oVirt Team: --- RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: --- Target Upstream Version:

Description bolotine 1999-07-14 18:06:38 UTC
I recently got this bad news message trying to boot:

		(i.e. without -a or -p options)

I think it would be a good idea if the message told users to
run	fsck.ext2.
fsck doesn't fix anything. The average newbie, home user
like myself, needs to experiment around to find the answer,
and that is not the best scenario, under the circumstances.

  I did manage to fix everything, except for one one file
left in /lost+found.

br-xr-srwT   1  17957   32545   101, 104 Sep 11 1994 #12601
which looks like it goes in /dev. Any idea of where I could
find out what the file name is?

Eric Bolotin

Comment 1 Jeff Johnson 1999-07-15 16:42:59 UTC
You can do
	rpm -V dev
to verify the dev package. However, the permissions are goofy
enough that it is unlikely that you lost+found file is "real" --
it's an inode that was damaged so the file type and mode happen
to be as displayed.

There are too many failure modes of a file system to be handled
with a better error message. The message that is displayed, while
uninformative, is at least constant (i.e. the same as its always