Linux - NewbieThis Linux forum is for members that are new to Linux.
Just starting out and have a question?
If it is not in the man pages or the how-to's this is the place!
Welcome to LinuxQuestions.org, a friendly and active Linux Community.
You are currently viewing LQ as a guest. By joining our community you will have the ability to post topics, receive our newsletter, use the advanced search, subscribe to threads and access many other special features. Registration is quick, simple and absolutely free. Join our community today!
Note that registered members see fewer ads, and ContentLink is completely disabled once you log in.
I am a new proud owner of a Linux Router/Firewall at my home. And I have to thank very much the Linuxquestions.org community and a special thank to Mara (moderator) for her patience and support.
But with every new solution, problems come along. And here it comes!!!
My Linux firewall doesn´t work on nobreaks (they are far too expensive here in Brazil for me to by one on a home basis), so sometimes the connection can drop because of electrical failures/blackouts... So, now I´m worried about the integrity of my file system and would like to know how can I monitor/fix file system inconsistencies?
Is there anything that works sort of like windows 95/98 scandisk?
I worry a lot about this because of the time and work put on to my router for it to work. So I would like to periodically (let´s say on a weekly basis, for a start) check for the integrity of my file system. :-)
You shouldn't run fsck on a mounted filesystem, like the message says (if you remount the filesystewm read only, though, it should be OK). Fsck will give you an option to run at boot if there's an unclean shutdown, before filesystems are mounted, if you choose, Generally, if you have a journalling filesystem like ext3 or reiserfs the chance of corruption is greatly lessened.
Buy an in-line UPS device. They are expensive but they are much better than stand-by UPS devices. An in-line UPS always draws its power from the battery while the battery is getting charged, so the computer power supply will get constant power. A stand-by UPS is just there waiting to make its move to switch from AC to battery. When it switches, there is a slight pause. Many power supplies have problems with this, so the computer could have some stability problems.
The ext3 filesystem is a journalizing filesystem If its unmounted uncleanly it recovers lost data from the journal. It will fsck itself after 30 days or so many mounts so you should'nt worry too much but forcing fsck wont hurt.
Well I did the "shutdown -Fr 0" and it started to work and did fine. It worked just like when the machine is booted unclean. And after that first part is started to show a lot of text I have never seened it. It´s really a lot of text/messages etc...
But the system halted at some place and this message appeared:
Recursive die failure, output supressed
<0> Kernel panic - not syncing: Fatal exception in interrupt.
For some reason when I put: shutdown -Fr 0 it goes all wrong (should work too). But when I put shutdown -Fr now, it works.
But I still need some help regarding the messages... My FC3 is in portuguese so I´ll try to write in an understandable way. I have two partitions in my Linux.
1 - Root partition (with all system files etc.);
2 - Home partition (all particular user files).
When I run reboot with fsck, the system show these messages:
Checking filesystem root 3.7% (non-contiguous).
Checking filesystem home 9.1% (non-contiguous).
Is this correct? I think the best choice would be to have nothing non-contiguous.
Another question is how can I put fsck to run on the next boot automatically, if the previous boot has been done unclean. It asks like this: Press a key in five second to run fsck. Or something like that. I want it to run imperatively.
If you don't mind reinstalling everything, I'd reccommend Debian. It has very fast boot and shutdown times, and it is very stable. Also, the filesystem has never been so corrupted that it took more than 30 seconds or so to repair it. I'd also reccommend ReiserFS. It's journal is much more comprehensive, it is more effieient and it is faster, too.