| Author |
Message |
taupehat
Joined: 01 May 2005
Posts: 31
|
| Posted: Thu May 29, 2008 11:55 pm Post subject: ext3_journal_start_sb: Detected aborted journal |
|
|
| Filesystem wipeout on a linode? Ouch! Managed to clear the busted journal using 'debugfs -w -R "feature ^has_journal,^needs_recovery" /dev/xvda' and now e2fsck -y is basically telling me I might as well run mke2fs. Alas. :( |
|
| Back to top |
|
Xan
Joined: 08 Feb 2004
Posts: 310
Location: Austin
|
| Posted: Fri May 30, 2008 1:50 am Post subject: |
|
|
| Wow. I've never heard of that on Linode (which probably means it isn't a Linode issue). It just goes to show, there is no replacement for frequent backups. I always appreciate people posting stories like this, because it gets me to make sure I've got everything adequately backed up. |
|
| Back to top |
|
taupehat
Joined: 01 May 2005
Posts: 31
|
| Posted: Fri May 30, 2008 11:00 am Post subject: |
|
|
| Well, the good news is that it was fixable. Some data hiccups, but it's alive now. Apparently this has happened on some xenodes with ext3fs using 1k block size. A big thank you to caker for his help with this last night - above and beyond the call, as usual! |
|
| Back to top |
|
| |
