cristian wrote:
> After ctrl+alt+del I got the message that I have to run fsck manually.
> I did fsck /dev/hda3
> I received messages:
> "Inode 350 has illegal blocks. Clear(y) YES
> Too many illegal blocks in inode 350. Clear(y) YES
> Restarting fsck from the beggining
> Entry 'tmp.wav' in / (2) has deleted/unused inode 350. Clear(y) YES
> Free blocks count wrong for group #0 (44, counted=644). Fix(y) YES
> .
> .
> follows many other similar messages, and then
> .
> Inode bitmaps differences: -350. Fix(y) YES
> /dev/hda3/ **FILE SYSTEM WAS MODIFIED"
>
> Then I rebooted and everything seems OK.
> Can someone explain me what is all this?
Well that's not serious, it's just that you rebooted your machine
wildly (hey, three-finger-salute ;).
When a program seems to write some things to the disk , kernel sometimes
put it in memory. At boot time, init runs kflushd, a flush daemon who
write things from mem to the disk. When you reboot hard, it can not
update the filesystem and so some inodes are f...(haem...) well some
inodes
are not up to date :). fsck solves this problems.
In fact, if after such problems you lost files, or find
your files in the state *before* you modified them,
go in the lost+found directory. In there some files with
esoteric numbers contain the data you "lost".
>
> Should I act otherway if it happens again?
No.You did well. :)
>
> How can I find out what is wrong with cd2amp3 ?
Well, that could be a lot of things. Do you have any additional info ?
It's a little bit hard to help you with things you gave.
--
Ismael
/* If God exists, it's a pretty good mathematician. */
