ext3_journal_start_sb: Detected aborted journal

Filesystem wipeout on a linode? Ouch! Managed to clear the busted journal using 'debugfs -w -R "feature ^hasjournal,^needsrecovery" /dev/xvda' and now e2fsck -y is basically telling me I might as well run mke2fs. Alas. :(

2 Replies

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.

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!

Reply

Please enter an answer
Tips:

You can mention users to notify them: @username

You can use Markdown to format your question. For more examples see the Markdown Cheatsheet.

> I’m a blockquote.

I’m a blockquote.

[I'm a link] (https://www.google.com)

I'm a link

**I am bold** I am bold

*I am italicized* I am italicized

Community Code of Conduct