From: Eric Sandeen <esandeen@redhat.com>
To: Julius Schwartzenberg <julius.schwartzenberg@gmail.com>,
linux-ext4@vger.kernel.org
Subject: Re: e2fsck doesn't finish
Date: Mon, 17 Apr 2017 14:16:26 -0500 [thread overview]
Message-ID: <059b964a-facb-cfd5-6691-4cc1d66fea61@redhat.com> (raw)
In-Reply-To: <f604727f-967c-0b49-a71c-f8adcaeb8945@gmail.com>
On 4/16/17 12:07 PM, Julius Schwartzenberg wrote:
> Hi all,
>
> I'm running into an e2fsck issue which seems to occur with one
> particular filesystem. The version from Ubuntu, Fedora and the latest
> release compiled from source all exhibit the same issue.
>
> On one filesystem I have, when I run e2fsck, it prints it's doing step 1
> and then after a while just:
> "e2fsck: aborted"
> Nothing else is printed. I tried a badblock scan on the partition, but
> that didn't reveal any badblocks.
>
> Here is the output of dumpe2fs:
> https://schwart6.home.xs4all.nl/dumpe2fs.sda4.gz
>
> I suspect there's some condition with that filesystem that e2fsck
> doesn't handle. What would be the best way to figure out more about this
> problem?
When I look at your image, it's finding tons of corruption - much
more than just "step 1" followed by "e2fsck: aborted"
If you didn't see that, then I wonder if e2image is not properly
handling your filesystem...
You might try running with the '-v' flag and see if it gives any
more hints about where it's at when it fails, and attach the
full e2fsck output to the next reply.
-Eric
next prev parent reply other threads:[~2017-04-17 19:16 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 [this message]
2017-04-18 5:24 ` Theodore Ts'o
2017-04-19 20:57 ` Julius Schwartzenberg
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=059b964a-facb-cfd5-6691-4cc1d66fea61@redhat.com \
--to=esandeen@redhat.com \
--cc=julius.schwartzenberg@gmail.com \
--cc=linux-ext4@vger.kernel.org \
--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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox