linux-ext4.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Pavel Machek <pavel@ucw.cz>
To: Andrey Melnikov <temnota.am@gmail.com>
Cc: jrf@mailbox.org, Theodore Ts'o <tytso@mit.edu>,
	linux-kernel@vger.kernel.org, linux-ext4@vger.kernel.org
Subject: Re: ext4 file system corruption with v4.19.3 / v4.19.4
Date: Tue, 11 Dec 2018 01:11:58 +0100	[thread overview]
Message-ID: <20181211001158.GA20388@amd> (raw)
In-Reply-To: <CA+PODjrT=pXg-jbhk=q=M6j6-v0x+c05s4Lmi3+MLm0P4iirqg@mail.gmail.com>

[-- Attachment #1: Type: text/plain, Size: 1147 bytes --]

Hi!

> > >> OK, - and now we are looking forward to *your* ideas how to solve this.
> > >
> > > After four days playing games around git bisect - real winner is
> > > debian gcc-8.2.0-9. Upgrade it to 8.2.0-10 or use 7.3.0-30 version for
> > > same kernel + config - does not exhibit ext4 corruption.
> > >
> > > I think I hit this https://gcc.gnu.org/bugzilla/show_bug.cgi?id=87859
> > > with 8.2.0-9 version.
> > >
> > Good that it works for you. But others used gcc 5.4.0 or 6.3.0 and were
> > hit anyway: https://bugzilla.kernel.org/show_bug.cgi?id=201685#c165
> 
> Depends on workload pattern. 4.19.5 built with 8.2.0-10 and 7.3.0-30 -
> crashed after 4 hours of usage (previous build crash in 5 min).
> So my assumption about broken gcc is wrong.

Would it be possible to try vanilla 4.19? (Not stable?)

I test vanilla and -next kernels every week or two, and did not have
ext4 problems recently. I guess many kernel developers test mainline
but not stable...

									Pavel
-- 
(english) http://www.livejournal.com/~pavelmachek
(cesky, pictures) http://atrey.karlin.mff.cuni.cz/~pavel/picture/horses/blog.html

[-- Attachment #2: Digital signature --]
[-- Type: application/pgp-signature, Size: 181 bytes --]

  reply	other threads:[~2018-12-11  0: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
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 [this message]
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=20181211001158.GA20388@amd \
    --to=pavel@ucw.cz \
    --cc=jrf@mailbox.org \
    --cc=linux-ext4@vger.kernel.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=temnota.am@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 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).