Last week my “storage” hard drive suffered from large amounts of corruption and this week, my “root” hard drive suffered the same fate. Luckly fsck was able to save my data in both cases but not without the trouble of having to run it, find the errors, correct them, add the fixed files to lost+found and then having to sort through the found files. It’s a horrible process because the whole time I don’t know how much of my data will be lost. Also fsck incapacitates my computer while it’s scanning.
There has to be a way around this. The corruption always seems to happen when Beagle is scanning. Both hard drives have the ext3 filesystem on them and both have extended attributes enabled so Beagle shouldn’t even be scanning! When the Beagle daemon is running, my hard drives are being accessed non-stop! Constant stress can’t be good for them and probably explains the corruption that happens right after Beagle is re-enabled.
Hopefully there is some fix to Beagle’s excessive scanning. Maybe there is a better filesystem that isn’t so prone to corruption? I’ll have to look into the problem more and find a way to diagnose whether it’s Beagle, ext3, or just my hardware. Until then, no Beagle for me.
- None Found