Hi! I have experienced inodes and ext filesystem corruption for quite a long time already. But since I recently installed a linux system on an old desktop. I realize the importance of filesystem corruption as a more important issue (before was just a nas machine, so I didn't care that much).
The slackware checks the disk whenever it is mounted 32 times (/dev/sda1). The last time I mounted, I saw a 0.9% contagious error on startup. Since I knew the e2fsck command, so I just repaired the disk, clearing the inodes. I have researched online that inodes are to do with the permission and path of the files in the filesystem. I am not sure if it is actually safe to just clear this information. What could I do if I experience this problem in the future?
I also realized that the NTFS and FAT disks don't have the same problem. I am sure that windows based filesystems have an analogous to this. But why doesn't a windows desktop prompt the same error?
Thanks,
Ted

Actually, the windows chkdsk (spelling ?) that comes up sometimes at boot is the analogous tool.
BTW I think you meant contiguous, not contagious

If you are worried that the disk is getting old, try http://linux.die.net/man/8/smartctl and also the disk manufacturer may have a tool you can use to chek.