On Thu, Nov 15, 2001 at 04:59:48AM -0000, Vandana Sudheer wrote: > > Hi, > > I am using Redhat 7.1 on an Intel celeron 333Mhz with > 128MB SDRAM. Today morning I came across this problem. > > UNEXPECTED INCONSISTENCY; Run fsck manually. Dropping you > to a shell > > Then I ran fsck /home with the following result. > > Then it fixed and cleared some file entries and saved some > data to lost+found directories and finished. Then I was > able to start my system, but I lost some while. > > My question is how this happened ? Is there some document > which will give me more information about this problem. > ---end quoted text---
There are absolutely NO problems here. This normally happens at boot. After the kernel loads, the init process starts. Integrity check of all ext2 partitions is done as per the set up of /etc/fstab. ( man fstab / mount for details) ... This error msg comes if there are problems within the ext2 filing systems. It is something akin to the scandisk which M$ systems do. This is a safety measure and is nothing to be bothered about .... There is a "count" also kept, usually 10 to 20 (depending upon your set up), after which you might get a message "maximum count reached ... ". This too is a part of normalcy. Think it as scandisk being run on the nth boot instead of at every boot ... and what goes into /lost+found is something like the .chk files that you may be familar with in the M$ systems. Unless text, you may rm all of them ... of no use really. Giving you a M$ analogy, because you are using a M$ mailer. HTH Bish -- : ####[ Linux One Stanza Tip (LOST) ]########################### Sub : Tips & Tricks for newbies LOST #038 Have a look at some excellent articles & newbie tips in the archives at : http://www.linux-mag.com/ ####<[EMAIL PROTECTED]>####################################### : _______________________________________________ linux-india-help mailing list [EMAIL PROTECTED] https://lists.sourceforge.net/lists/listinfo/linux-india-help
