From: "Theodore Y. Ts'o" <tytso@mit.edu>
To: Rainer Fiebig <jrf@mailbox.org>
Cc: linux-kernel@vger.kernel.org,
"Andrey Jr. Melnikov" <temnota.am@gmail.com>,
linux-ext4@vger.kernel.org
Subject: Re: ext4 file system corruption with v4.19.3 / v4.19.4
Date: Wed, 28 Nov 2018 11:10:33 -0500 [thread overview]
Message-ID: <20181128161033.GH31885@thunk.org> (raw)
In-Reply-To: <2547416.7Vy7A2kRpU@siriux>
On Wed, Nov 28, 2018 at 04:56:51PM +0100, Rainer Fiebig wrote:
>
> If you still see the errors, at least the Ubuntu-kernel could be ruled out.
My impression is that some of the people reporting problems have been
using stock upstream kernels, so I wasn't really worried about the
Ubuntu kernel (although it could be something about the default
configs that Ubuntu sets up). What I was more wondering was whether
there was something about userspace or default configs of Ubuntu.
This isn't necessarily a *problem* per se; for examople, not that long
ago some users were getting surprised when a problem showed up with an
older version of the LVM2 userspace with newer upstream kernels.
After a while, you learn to get super paranoid about making sure to
rule out all possibilities when trying to debug problems that are only
hitting a set of users.
- Ted
next prev parent reply other threads:[~2018-11-29 3:12 UTC|newest]
Thread overview: 25+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-11-27 12:22 ext4 file system corruption with v4.19.3 / v4.19.4 Guenter Roeck
2018-11-27 14:32 ` Guenter Roeck
2018-11-27 14:48 ` Marek Habersack
2018-11-27 17:31 ` Guenter Roeck
2018-11-27 18:55 ` Rainer Fiebig
2018-11-27 21:22 ` Guenter Roeck
2018-11-28 1:57 ` Vito Caputo
2018-11-28 9:56 ` Rainer Fiebig
2018-11-27 15:50 ` Rainer Fiebig
2018-11-28 0:16 ` Andrey Jr. Melnikov
2018-11-28 4:15 ` Theodore Y. Ts'o
2018-11-28 8:02 ` Marek Habersack
2018-11-28 10:02 ` Andrey Jr. Melnikov
2018-11-28 15:56 ` Rainer Fiebig
2018-11-28 16:10 ` Theodore Y. Ts'o [this message]
2018-11-28 16:18 ` Marek Habersack
2018-11-28 17:01 ` Rainer Fiebig
2018-11-28 21:13 ` Andrey Melnikov
2018-11-28 22:09 ` Rainer Fiebig
2018-12-02 20:19 ` Andrey Melnikov
2018-12-02 22:13 ` Rainer Fiebig
2018-12-05 12:58 ` Andrey Melnikov
2018-12-11 0:11 ` Pavel Machek
2018-12-13 10:38 ` Andrey Jr. Melnikov
2018-11-28 13:28 ` Andrey Melnikov
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=20181128161033.GH31885@thunk.org \
--to=tytso@mit.edu \
--cc=jrf@mailbox.org \
--cc=linux-ext4@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=temnota.am@gmail.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;
as well as URLs for NNTP newsgroup(s).