From: Bernd Schubert <bernd.schubert@fastmail.fm>
To: Eric Sandeen <sandeen@redhat.com>,
Regan Wallace <regan@reganw.com>,
linux-ext4@vger.kernel.org, "Darrick J. Wong" <djwong@us.ibm.com>
Subject: Re: Filesystem recovery - e2fsck seems to have caused my filesystem to get wiped
Date: Wed, 30 Oct 2013 17:00:04 +0100 [thread overview]
Message-ID: <52712D04.1030104@fastmail.fm> (raw)
In-Reply-To: <5271297B.7040101@redhat.com>
>
> # tune2fs -f -O ^has_journal sda1.img
> tune2fs 1.41.12 (17-May-2010)
> The needs_recovery flag is set. Please run e2fsck before clearing
> the has_journal flag.
>
> nope, not even with force. Grr.
>
> Maybe this will work; get the journal inode number & clear it:
>
> # dumpe2fs -h sda1.img | grep "Journal inode"
> dumpe2fs 1.41.12 (17-May-2010)
> Journal inode: 8
>
> # debugfs -w -R "clri <8>" sda1.img
>
> now e2fsck will think the journal is invalid & just zap it:
>
> e2fsck 1.41.12 (17-May-2010)
> Superblock has an invalid journal (inode 8).
> Clear<y>?
>
> *maybe* that will get your e2fsck past the journal recovery problem
> w/o needing the mkfs.ext4 -S giant hammer.
Why not just unset the journal feature bit using debugfs?
debugfs -w -R "features ^has_journal" sda1.img
And I would update e2fsprogs to the current version.
Cheers,
Bernd
next prev parent reply other threads:[~2013-10-30 16:00 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <868818551.88.1383137282029.JavaMail.root@reganw.com>
2013-10-30 13:08 ` Filesystem recovery - e2fsck seems to have caused my filesystem to get wiped Regan Wallace
2013-10-30 15:44 ` Eric Sandeen
2013-10-30 16:00 ` Bernd Schubert [this message]
2013-10-30 16:14 ` Eric Sandeen
2013-10-30 17:50 ` Darrick J. Wong
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=52712D04.1030104@fastmail.fm \
--to=bernd.schubert@fastmail.fm \
--cc=djwong@us.ibm.com \
--cc=linux-ext4@vger.kernel.org \
--cc=regan@reganw.com \
--cc=sandeen@redhat.com \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.