On Mon, 12 Feb 2001, Neeraj Manral wrote:
> i>Why did this happen !
It happens simply if the filesystem check fails. Now it can happen
due to many of the reasons, which I can't detail out because of my meagre
knowledge of filesystem internels :(
You have more chances of it happening if you switch off the system
without a proper shutdown. ( I think because the disk has not synced
etc..) So, you should do a proper shutdown .
> ii>was it the fsck -A that rectified the problem or the mount command.Or
> both.
fsck -A means check all the filesystems. You generally can get
away with checking only the filesystem which caused problem. And it is the
fsck which corrects the fs. It was only that fs was mounted read-only to
protect it from further damage.
>
> iii>In the archives i read that while booting if linux gets struk fsck -A
> does not work .what other options are there ?Is there some thing like
> manually and automatically in fsck command..
Yes, fsck -a is automatic. But it is not recommended probably
because the linux developers feel all the users are expers too :) Although
I just type yes for everything and hoping it will correct the problem.
> iv>what should one do in such a situation ?
Other problems are really other problems and don't have anything
to do with filesystems. You may have a perfect filesystem but you mbr may
be corrupt :( and if any problem occurs you can run to LIH just like me :)
bye and Enjoy life. (And do a proper shutdown next time :)
--
#!!! If anything can go wrong, _FIX_ it. (To hell with MURPHY)
Ajay kumar Dwivedi
[EMAIL PROTECTED]
----------------------------------------------
The mailing list archives are available at
http://lists.linux-india.org/cgi-bin/wilma/linux-india-help
