Well, I've got the problem that two of my filesystems have got INode errors (altough I shut down Linux correctly) and `e2fsck -p` told me that I have to run `fsck` _Manually_.
The problem here is, that these two filsystems have some hundred thousand of Inodes... checking this manually is kind of ... impossible?
So my only option is to use `fsck.ext3 -y /dev/hdf6` - but in the man-pages of the `fsck`-command they say that the `-y` option (automatically answer all questions with "yes") shouldn't be used (maybe because of data-loss?).
So is this command secure or will I suffer several Data loss?
Maybe there is another filesystem-checking program?

Thanks & bye bye~,
MHOOO

You should dump all your data to another disk before you touch it with anything. You can do a raw dump by doing:
That is, if you value your data. I think it's always a good idea to make a backup. That said, I have never had a problem with fsck -y.

Hmm, maybe it's just me, but I've had filesystem-errors already several times - altough I _always_ shut down Linux correctly. Doing a backup every week after a Linux shutdown somehow seems like mutch work to do... - well, the Data (~50-100GB) isn't that important at the moment, since I'm currently only testing... but I'm somehow worried.
Why exactly are there Errors even though I shut down Linux correctly?
On one partition I only copied once through Samba some Data (30GB) - I didn't do anything else with it - where do those errors come from?
On the other partition I copy automatically Data every day ~1-2GB.
Is Linux maybe bad at Handling big amounts of Data?

Well, I ran `fsck -y`just now on both Drives - and after some file-checks there actually really was some Data loss (several hundreds of MB). How come I loose that mutch Data altough I could access all that Data when the System was still running - maybe there is a way to prevent this _before_ shutting down Linux?

Thanks & bye bye~,
MHOOO

How exactly are you shutting down Linux? I've only ever experienced data loss when one of my systems has gone down uncleanly, e.g. due to a power failure. Even then, with journalling filesystems I've never actually lost anything.

If this is a persistant problem, your hard drive and/or disk controller may be on its way out. You should probably run badblocks on your hard disks. If there are lots of bad blocks found, it's time to buy a new disk.

`shutdown -h now` or sometimes `reboot` (should be the same either way).
Scanned my HD 2 weeks ago for Badblocks using the destructive read-write (`-cc`) mode in the `badblocks` program.
Scanned for corrupt sectors with Partition Magic 8 and Partition Doctor 3.
Nothing found...
I somehow can't believe it's a problem with my HD - since I bought it just a month ago (WD2000JB - Western Digital 200GB).

Thanks & bye bye~,
MHOOO