public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: Marek Habersack <grendel@twistedcode.net>
To: "Theodore Y. Ts'o" <tytso@mit.edu>,
	"Andrey Jr. Melnikov" <temnota.am@gmail.com>,
	linux-kernel@vger.kernel.org, linux-ext4@vger.kernel.org
Subject: Re: ext4 file system corruption with v4.19.3 / v4.19.4
Date: Wed, 28 Nov 2018 09:02:05 +0100	[thread overview]
Message-ID: <5d21196e-15d5-3351-e431-576d3640387f@twistedcode.net> (raw)
In-Reply-To: <20181128041555.GE31885@thunk.org>

On 28/11/2018 05:15, Theodore Y. Ts'o wrote:
> On Wed, Nov 28, 2018 at 03:16:33AM +0300, Andrey Jr. Melnikov wrote:
>> Corrupted inodes - always directory, not touched at least year or
>> more for writing. Something wrong when updating atime?
I've just seen the errors come back despite having MQ off :( However, this time it took 5 days for them to come back, so
MQ must play a role here. Also, indeed, they happened after fstrim ran and this time *only* on the SSD disks reported
below, another clue? This time the errors were "just" orphaned inodes + invalid free inode counts, all repaired without
issues by fsck.

> 
> We're not sure.  The frustrating thing is that it's not reproducing
> for me.  I run extensive regression tests, and I'm using 4.19 on my
> development laptop without notcing any problems.  If I could reproduce
> it, I could debug it, but since I can't, I need to rely on those who
> are seeing the problem to help pinpoint the problem.
> 
> I'm trying to figure out common factors from those people who are
> reporting problems.
> 
> (a) What distribution are you running (it appears that many people
> reporting problems are running Ubuntu, but this may be a sampling
> issue; lots of people run Ubuntu)?  (For the record, I'm using Debian
> Testing.)
Ubuntu 18.10 here

> 
> (b) What hardware are you using?  (SSD?  SATA-attached?
> NVMe-attached?)
The errors occured on both SSD:
  - Samsung SSD 850 EVO 1TB, firmware rev EMT03B6Q
  - OCZ-AGILITY3, firmware rev 2.25

and spinning rust:
  - Seagate ST2000DX001-1CM164, firmware revision CC43

> 
> (c) Are you using LVM?  LUKS (e.g., disk encrypted)?
LUKS. Both the Samsung and the Seagate use DM for encryption.

> (d) are you using discard?  One theory is a recent discard change may
> be in play.   How do you use discard?   (mount option, fstrim, etc.)
fstrim runs weekly and the Samsung SSD is mounted with

   rw,nosuid,nodev,noatime,discard,helper=crypt

marek
> 
>       	      	     	     		- Ted
> 


  reply	other threads:[~2018-11-28  8:02 UTC|newest]

Thread overview: 27+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <065643a0-f9aa-a361-715a-03ca978d9228@roeck-us.net>
2018-11-27 14:32 ` ext4 file system corruption with v4.19.3 / v4.19.4 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 [this message]
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
2018-12-13 10:38                       ` Andrey Jr. Melnikov
2018-11-28 13:28       ` Andrey Melnikov
2018-12-01 15:47 Huang Yan
  -- strict thread matches above, loose matches on Subject: below --
2018-12-03 21:47 Michael Hennig
2018-12-04  7:33 Gunter Königsmann

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=5d21196e-15d5-3351-e431-576d3640387f@twistedcode.net \
    --to=grendel@twistedcode.net \
    --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