From: Theodore Ts'o <tytso@mit.edu>
To: Bo Branten <bosse@acc.umu.se>
Cc: linux-ext4@vger.kernel.org
Subject: Re: found an error that e2fsck does not fix
Date: Sat, 28 Nov 2015 07:27:47 -0500 [thread overview]
Message-ID: <20151128122747.GA2836@thunk.org> (raw)
In-Reply-To: <alpine.DEB.2.10.1511272003250.1707@suiko.acc.umu.se>
On Fri, Nov 27, 2015 at 08:11:34PM +0100, Bo Branten wrote:
>
> I am debugging an Windows driver for ext4 and when creating an zero length
> file the error below shows up on Linux, while this ofcause is an bug in the
> Windows driver (looks like it forgets to flush some metadata) I wanted to
> report here that every time I run fsck on this test volume it will mark it
> as clean again but without fixing the error, so if I mount and unmount the
> filesystem again it is again in need of fsck wich in turn will mark it clean
> witout fixing the problem.
>
> Test case, testa and testb is created from Windows and only testb gets one
> character written to with notepad:
This test case doesn't really help since I don't have access to your
potentially buggy Windows driver for ext4.
What would be helpful:
(a) the output of "e2fsck -fy /dev/sdXX" run twice. If e2fsck isn't
fixing a problem, then a forced check should show it trying to fix the
problem again. Also the exact output of what e2fsck prints would be
heplful. It's possible that mounting and unmounting the file system
using the Windows driver is causing the problem, so running "e2fsck
-fy" twice in succeession will determine whether or not this is the
case. In general, "e2fsck -fy" should fix all corruptions in a single
run. So a second run of "e2fsck -fy", if it shows errors, is an
indication of either (a) a hardware problem (e.g., so an update of the
file system image is getting lost or the disk image is geting
changed/corrupted between runs of e2fsck), or (b) a bug in e2fsck.
(b) See the REPORTING BUGS section of the e2fsck man page; in
particular, note its suggestion to use e2image. The e2image man page
will have more details, but the short version is to send me the output
of "e2image -r /dev/sdXX - | bzip2 > sdXX.e2i.bz2".
If you can reproduce the problem on an arbitrary file system, create a
small test file system "mke2fs -b 4096 /dev/sdXX 1M" and then either
use the e2image directions described above to send me a minimal test
case.
Thanks,
- Ted
next prev parent reply other threads:[~2015-11-28 12:27 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-11-27 19:11 found an error that e2fsck does not fix Bo Branten
2015-11-28 12:27 ` Theodore Ts'o [this message]
2015-11-28 18:08 ` Bo Branten
2015-11-28 21:49 ` 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=20151128122747.GA2836@thunk.org \
--to=tytso@mit.edu \
--cc=bosse@acc.umu.se \
--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