From: Julius Schwartzenberg <julius.schwartzenberg@gmail.com>
To: Theodore Ts'o <tytso@mit.edu>, sandeen@redhat.com
Cc: linux-ext4@vger.kernel.org
Subject: Re: e2fsck doesn't finish
Date: Wed, 19 Apr 2017 22:57:00 +0200 [thread overview]
Message-ID: <46831715-eb83-51b3-a626-7f6669b02e8a@gmail.com> (raw)
In-Reply-To: <20170418052415.jl44dt2jnmclpx5m@thunk.org>
Theodore Ts'o wrote:
> It looks like the problem is fixed with the latest version of
> e2fsprogs, though. I just tried running using a build of e2fsprogs
> from the next branch, and this seems to allow e2fsck to fully fix the
> file system and avoid the "aborted" message.
I just tried the latest e2fsck from git and it indeed fully got through.
I'm really glad here and I hope there will be a new release of e2fsprogs
soon!
I still have a (dd) copy of the original full image on my external hard
drive in case it would be useful.
I don't know if this is relevant, but maybe it could also be related to
a conversion? Till recently the filesystem was still ext3 and I was only
using it from Ubuntu 16.04. After installing Fedora 25 on another
partition, Ubuntu couldn't mount this partition anymore and I had to
change its entry in /etc/fstab from ext3 to ext4. Then it could mount
it, but Ubuntu's e2fsck complained there were features in use that it
didn't support. I reported this Fedora bug then:
https://bugzilla.redhat.com/show_bug.cgi?id=1440429
After I reported bug, I ran into the issues with e2fsck failing to complete.
In any case, thanks a lot Theodore and Eric for looking into this! My
issue is solved now, but if there's anything that would still be useful
to figure out I'll be glad to provide any information that could help.
Thanks!
Julius
next prev parent reply other threads:[~2017-04-19 20:57 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-04-16 17:07 e2fsck doesn't finish Julius Schwartzenberg
2017-04-17 14:17 ` Eric Sandeen
2017-04-17 15:11 ` Julius Schwartzenberg
2017-04-17 15:18 ` Eric Sandeen
2017-04-17 19:16 ` Eric Sandeen
2017-04-18 5:24 ` Theodore Ts'o
2017-04-19 20:57 ` Julius Schwartzenberg [this message]
2017-04-19 21:07 ` Andreas Dilger
2017-04-23 14:07 ` Julius Schwartzenberg
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=46831715-eb83-51b3-a626-7f6669b02e8a@gmail.com \
--to=julius.schwartzenberg@gmail.com \
--cc=linux-ext4@vger.kernel.org \
--cc=sandeen@redhat.com \
--cc=tytso@mit.edu \
/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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox