From: Julius Schwartzenberg <julius.schwartzenberg@gmail.com>
To: linux-ext4@vger.kernel.org
Subject: Re: e2fsck doesn't finish
Date: Mon, 17 Apr 2017 17:11:55 +0200 [thread overview]
Message-ID: <deffb0af-1aaf-bad9-a7e5-64ea39171aa1@gmail.com> (raw)
In-Reply-To: <f5fb3216-c52c-fc63-d90b-e6f670843882@redhat.com>
Eric Sandeen wrote:
> Providing an e2image might allow developers to analyze the problem.
> If it's a large filesystem, the qcow output format is most portable.
Here is the e2image:
https://schwart6.home.xs4all.nl/sda4.e2i.bz2
The file is around 150M.
It's made with -s as the file system concerned is actually /home on my
notebook.
Thanks,
Julius
next prev parent reply other threads:[~2017-04-17 15:11 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 [this message]
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
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=deffb0af-1aaf-bad9-a7e5-64ea39171aa1@gmail.com \
--to=julius.schwartzenberg@gmail.com \
--cc=linux-ext4@vger.kernel.org \
/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