Ever since I started using the Raspberry Pi, I’m loosing it’s Filesystem’s within a few weeks of running time. It’s annoying beyond telling :-(
Initially, I lost the RPi’s root filesystems when they were ext4 — thus I switched back to ext3. But that’s no use on the Raspberry Pi either:
Aug 25 00:27:09 ysabell kernel: [69615.118808] EXT3-fs error (device sdb2): ext3_check_descriptors: Block bitmap for group 64 not in group (block 3145728)! Aug 25 00:27:09 ysabell kernel: [69615.118821] EXT3-fs (sdb2): error: group descriptors corrupted
Nice. Amazing actually, it’s the fourth or fifth time on different Pis this happened :-( Well, let’s give fsck a try:
File /etc/gconf/2/path (inode #1285082, mod time Mon Mar 4 22:00:37 2013) has 1 multiply-claimed block(s), shared with 1 file(s): /etc/apache2/conf.d/security (inode #1285086, mod time Mon Mar 4 22:00:37 2013) Clone multiply-claimed blocks? yes File /etc/samba (inode #1285083, mod time Sat Dec 15 18:38:22 2012) has 1 multiply-claimed block(s), shared with 1 file(s): /etc/cron.weekly (inode #1285087, mod time Sat Dec 15 18:38:22 2012) Clone multiply-claimed blocks? yes File /lib/udev/rules.d/95-upower-battery-recall-fujitsu.rules (inode #156858, mod time Fri Jul 6 12:52:01 2012) has 1 multiply-claimed block(s), shared with 1 file(s): /lib/udev/rules.d/95-upower-battery-recall-ibm.rules (inode #156850, mod time Fri Jul 6 12:52:01 2012) Multiply-claimed blocks already reassigned or cloned. File /lib/udev/rules.d/60-persistent-alsa.rules (inode #156853, mod time Mon Aug 27 15:53:27 2012) has 7 multiply-claimed block(s), shared with 1 file(s): /lib/udev/pci-db (inode #156861, mod time Mon Aug 27 15:53:27 2012) Clone multiply-claimed blocks? yes
Seriously? Why? What the heck is that moron writing there? I mean, come one, none of them, and there were a lot more of similar errors, has been written to or been modified recently. Why is the Raspberry Pi/Raspian Linux trashing filesystems (on SD) when nothing similar has yet happened to any other system I use? Even on the MK802, which I tend to power-off instead of properly shutting down occasionally (well, there’s no choice if you lost connectivity to it, is there) did not exhibit this behaviour (yet). But the Raspberry Pi does, all the time. It certainly feels as if too much stuff is held in RAM instead on the SD card, at least that’s the last time i suffered that badly from filesystem inconsistency (rewind 15+ years, me fiddeling with Sun E450′s to cope with the news volume at that time, years before INN was patched with News-in-Dosen …).