From: Ondrej Zary <linux@zary.sk>
To: Arthur Marsh <arthur.marsh@internode.on.net>
Cc: "Theodore Ts'o" <tytso@mit.edu>,
Richard Weinberger <richard.weinberger@gmail.com>,
LKML <linux-kernel@vger.kernel.org>,
linux-ext4@vger.kernel.org
Subject: Re: ext3/ext4 filesystem corruption under post 5.1.0 kernels
Date: Tue, 14 May 2019 12:42:39 +0200 [thread overview]
Message-ID: <201905141242.39800.linux@zary.sk> (raw)
In-Reply-To: <850EDDE2-5B82-4354-AF1C-A2D0B8571093@internode.on.net>
On Tuesday 14 May 2019, Arthur Marsh wrote:
> Apologies, I had forgotten to
>
> got bisect - - hard origin/master
>
> I am still seeing the corruption leading to the invalid block error on 5.1.0+ kernels on both my machines.
>
> Arthur.
I've been probably hit by the same bug. ext3 filesystem on my test machine was corrupted twice with 5.1.0+. Only the corruption was heavier. Some files that were open (e.g. logs) became cros-linked with files that were not used for ages.
--
Ondrej Zary
next prev parent reply other threads:[~2019-05-14 11:01 UTC|newest]
Thread overview: 16+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-05-11 11:33 ext3/ext4 filesystem corruption under post 5.1.0 kernels Arthur Marsh
2019-05-11 12:43 ` Richard Weinberger
2019-05-11 22:06 ` Theodore Ts'o
2019-05-13 7:45 ` Arthur Marsh
2019-05-13 10:31 ` Arthur Marsh
2019-05-14 1:59 ` Arthur Marsh
2019-05-14 10:42 ` Ondrej Zary [this message]
2019-05-15 2:59 ` Arthur Marsh
2019-05-15 4:57 ` Theodore Ts'o
2019-05-15 12:12 ` Arthur Marsh
2019-05-16 2:56 ` Theodore Ts'o
2019-05-17 16:44 ` Geert Uytterhoeven
2019-07-01 12:43 ` Geert Uytterhoeven
2019-07-01 13:56 ` Theodore Ts'o
2019-07-01 14:08 ` Geert Uytterhoeven
2019-05-17 9:23 ` Geert Uytterhoeven
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=201905141242.39800.linux@zary.sk \
--to=linux@zary.sk \
--cc=arthur.marsh@internode.on.net \
--cc=linux-ext4@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=richard.weinberger@gmail.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 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.