> Hmm... is there any chance that a rtorrent was in the middle of > downloading a file at the time when you shutdown the system? If so, > try killing all processes which might be writing to the filesystem > (especially any rtorrent processes) before shutting down the > filesystem. Zero. I carefully quit rtorrent everytime I reboot, including this one. If I ever forget to, I'll notice right away the moment I start it, because it'd rehash everything. I forgot to menction something that might be key, which is that a few reboots ago, I couldn't reboot (reboot wouldn't finish) until I forced it with with -f and another parameter which makes reboot not sync before rebooting. Doing a sync in another terminal never finished, so the FS got stuck somehow. The error might have started appearing immediatly after that. > Another question is whether mounting -o nodelalloc (on the previous > boot session) makes the problem go away. These last two tries are > based on the assumption that the filesystem is somehow really getting > corrupted on shutdown, and since you have errors=continue, it's > getting silently fixed up in mballoc.c, and so it doesn't show up when > you unmount the filesystem and run e2fsck. If this assumption is > true, that bogus free blocks in the superblock should show up in the > dumpe2fs, and it should also show up when you reboot via a rescue disk > and run "e2fsck -nfv /dev/sda3". I'll do the later at next opportunity, also the other thing we discussed on irc. > - Ted > -- To unsubscribe from this list: send the line "unsubscribe linux-ext4" in the body of a message to majordomo@xxxxxxxxxxxxxxx More majordomo info at http://vger.kernel.org/majordomo-info.html
