[MPlayer-users] Re: weird behavior

[Stefan Seyfried]

Sebastian Kaps <seb-keyword-mplayer.729994 at toyland.sauerland.de> writes:
 
> Actually some of the files are from after the crash so they couldn't
> have been affected directly. But I just noticed a huge difference in the
> file sizes shown by 'ls' and 'du'. ls says the file is ~720 MB big, du
> only says 420 MB.
> I now remember that I had to run a fsck again one or two days after the
> crash. It seems that this corrupted the files.

A bad filesystem crash, especially when caused by bad software (experimental
kernel) or bad hardware (often seemingly unrelated, e.g. bad ram or a bad
disk cable) is always a reason for me to back up everything to a second
machine and then mkfs and restore, or just reinstall and restore your
data files.

Especially on those modern journaling filesystems it happened to me more
than once that these started "rotting" after a seemingly repaired bad
corruption, symptoms were seemingly random disappearing files or that
audio files became "glitchy" although i knew they were once in good shape
since i ripped them from my own CDs. Since then, i tend to use the "old
fashioned" Filesystems like ext2 on really important machines and data
(which in turn often arent hundreds of gigabytes, my _really_ important
data still would fit easily on one of those 40MB mini CDs) and use the
ext3/reiser/whatever for those 180GB disks where the less important
data is stored.

just a hint...

-- 
 Stefan Seyfried, seife at gmane0305.slipkontur.de
+----------------------------------------------+

"If you want to travel around the world and be invited to speak at a lot of
 different places, just write a Unix operating system." -- [Linus Torvalds]