On Fri, 22 Sep 2000 [EMAIL PROTECTED] wrote:
>> reconfigure everything each time, spending 10-30 minutes to learn
>> how to use fsck and print out the manpage is nothing. That was
>> my main point. I'm just trying to offer help to the real
>> solution thats all. Nobody has to follow it.. ;o)
>>
>
>Knowing fsck is useless because the real problem is that it gives you
>messages like "inode 43200 has such problem do you want I do this?".
>Now hhow do you know what is inode 43200? You are not in normal mode
>with a process controlling the terminal so CTRL-C and CTRL-Z are
>unavailable and that means you cannot suspend fsck and use find to
>know what is this inode. In addition the partition is not even
>mounted. All you can do is answer blindly.
No, there are other things you can do too. It requires that you
know more about the filesystem however. If you truely don't know
the filesystem and what to answer, then it is guesswork. What do
you expect from guesswork? As long as you use ext2, or other
filesystems (most?) that aren't journalled, if you have power
outages or similar problems you will have fsck running. If any
problems arise, you either know what to do, or guess, or both.
fsck is only one tool, debugfs is another, the latter requires
deeper fs knowledge however. If one finds themselves frequently
experiencing corruption problems, it might pay to learn the
filesystem internals. A good day or two's reading I believe
should give plenty of info to handle most situations. There are
several howto's, and on the web there are ext2 documents by Ted
T'so I believe, and perhaps others.. I've got a few kicking
around. ext2 isn't that hard to understand, although I'm a bit
rusty on it right now since I haven't had to use debugfs in over
3 years. ;o)
--
Mike A. Harris - Linux advocate - Open source advocate
Copyright 2000 all rights reserved
----------
Want to try a new high performance open source web server? Try Caudium!
http://caudium.org http://caudium.sourceforge.net
_______________________________________________
Redhat-devel-list mailing list
[EMAIL PROTECTED]
https://listman.redhat.com/mailman/listinfo/redhat-devel-list
