Submit Hint Search The Forums LinksStatsPollsHeadlinesRSS
14,000 hints and counting!

Click here to return to the 'Use fsck to find troublesome files' hint
The following comments are owned by whoever posted them. This site is not responsible for what they say.
Use fsck to find troublesome files
Authored by: dand on Oct 31, '03 08:29:35PM

I was having trouble with my iBook (in 10.2.6 and 10.2.8 with journalling enabled) whenever I tried to boot into OS 9. Often, but not always, it would get stuck during the boot with a flashing question-mark disk icon. Booting from a backup HD, I ran fsck on my internal drive and I got a couple of "overlapping extent files" errors. fsck did not fix these after numerous attempts.

Finally I found some piece of information online that suggested these bad files were created by certain Limewire downloads. The problem was fixed by removing the bad files after looking up their inode numbers ("find / -inum ###" I believe). At least it appears to be fixed for the moment...

So the moral of the story is, it may be wise to run fsck -fn every once in a while even if you have a journalled drive.

[ Reply to This | # ]