Received: by 2002:ad5:474a:0:0:0:0:0 with SMTP id i10csp691114imu; Tue, 27 Nov 2018 20:17:27 -0800 (PST) X-Google-Smtp-Source: AFSGD/Xs8VmPtvUDlnuuwaGH88Lf1t94AsBZv2QLvTLkYkRzwIo8HDeJ4LK9BszCZ7uWXW5RVAg3 X-Received: by 2002:a17:902:d70b:: with SMTP id w11mr21252209ply.294.1543378647820; Tue, 27 Nov 2018 20:17:27 -0800 (PST) ARC-Seal: i=1; a=rsa-sha256; t=1543378647; cv=none; d=google.com; s=arc-20160816; b=NAayozzJybSXcWlvGHMJWKM2avPtHnl+PcA6KYmskETyJdv1eNMVMlf71W/l0zxK0b kT8HvWrc2Ep1kRr9DqwPt3/kt7mXDdWJ0guMkD6cv2YgL9LYLFCr5Jw351eSb0FL27JJ DBBuxUcAfBiD5RT393xsDUVde/Si8JkijOrW3rApEK2SyVU/IVvonIhjXMYRMQX07vNe xbQWn/B0ruZwxEYWBNHYvPpka3de/Xtxdw2Xd8mVTHldxycPDe/xm8DfZnAkj5wzZWpB 4FYGnReiN7FtC6va1ttoCNNnWeoxYn4qszy4z54reURo2O7l3nOodMNoPVMydbrGwmFN xdnw== ARC-Message-Signature: i=1; a=rsa-sha256; c=relaxed/relaxed; d=google.com; s=arc-20160816; h=list-id:precedence:sender:user-agent:in-reply-to :content-disposition:mime-version:references:mail-followup-to :message-id:subject:cc:to:from:date:dkim-signature; bh=ShC3vw5K4CyDFKR/hXxciFMfT9v0P8PFhwufBD74RVM=; b=hMWO5Yv3dgISlCV6VvzJkmc/vDQ8R5kPhP1ECyoYKeaHg7Qx4sY9mhtuFFtYtrsFDo h55SHUrKncTlQc4CKzEShC+9eiPyevenB2NkZajgXiBysDl/C1t38skGoB0j9SujjDU+ VYKqGYeARBGk4J+HnpjBB23/m0J5A5e0EyOozklbL78wmim+GKLBImUH2ElPnzSnLecr tRsbOGyzENXtKlQJDoOVkW0u0vDKp0NolfJm2XxJCPbY6JlXyWZRnLE1kNlhP2dwAuxh DIHa9157ogv8mkpv07gbjOvgFL8j5XIrELfuZ4Ml7ekJNUwVtEKjqq2Ql5SM4WbfGx86 GIbg== ARC-Authentication-Results: i=1; mx.google.com; dkim=fail header.i=@thunk.org header.s=ef5046eb header.b="ckFxk0/i"; spf=pass (google.com: best guess record for domain of linux-kernel-owner@vger.kernel.org designates 209.132.180.67 as permitted sender) smtp.mailfrom=linux-kernel-owner@vger.kernel.org Return-Path: Received: from vger.kernel.org (vger.kernel.org. [209.132.180.67]) by mx.google.com with ESMTP id v5si5740580plo.247.2018.11.27.20.17.13; Tue, 27 Nov 2018 20:17:27 -0800 (PST) Received-SPF: pass (google.com: best guess record for domain of linux-kernel-owner@vger.kernel.org designates 209.132.180.67 as permitted sender) client-ip=209.132.180.67; Authentication-Results: mx.google.com; dkim=fail header.i=@thunk.org header.s=ef5046eb header.b="ckFxk0/i"; spf=pass (google.com: best guess record for domain of linux-kernel-owner@vger.kernel.org designates 209.132.180.67 as permitted sender) smtp.mailfrom=linux-kernel-owner@vger.kernel.org Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S1727339AbeK1PQJ (ORCPT + 99 others); Wed, 28 Nov 2018 10:16:09 -0500 Received: from imap.thunk.org ([74.207.234.97]:37106 "EHLO imap.thunk.org" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1726989AbeK1PQI (ORCPT ); Wed, 28 Nov 2018 10:16:08 -0500 DKIM-Signature: v=1; a=rsa-sha256; q=dns/txt; c=relaxed/relaxed; d=thunk.org; s=ef5046eb; h=In-Reply-To:Content-Type:MIME-Version:References:Message-ID: Subject:Cc:To:From:Date:Sender:Reply-To:Content-Transfer-Encoding:Content-ID: Content-Description:Resent-Date:Resent-From:Resent-Sender:Resent-To:Resent-Cc :Resent-Message-ID:List-Id:List-Help:List-Unsubscribe:List-Subscribe: List-Post:List-Owner:List-Archive; bh=ShC3vw5K4CyDFKR/hXxciFMfT9v0P8PFhwufBD74RVM=; b=ckFxk0/iTrC6Tpmwe79tanW2nq T4c09gcixH7bxAap5sBTKgqW54IGiDG0aMgTkFnWXEbaa9HRCuKtwADomG2UqfspBgS6+fIYvh/pW iiB3bEMCcGRXoTffhnyV8rbPICh6JjsxK2OlrSFiP6uzNKVnhgZqkR/X1xlW4l4VAfHc=; Received: from root (helo=callcc.thunk.org) by imap.thunk.org with local-esmtp (Exim 4.89) (envelope-from ) id 1gRrGW-0008Hl-Nc; Wed, 28 Nov 2018 04:15:56 +0000 Received: by callcc.thunk.org (Postfix, from userid 15806) id A98557A46FC; Tue, 27 Nov 2018 23:15:55 -0500 (EST) Date: Tue, 27 Nov 2018 23:15:55 -0500 From: "Theodore Y. Ts'o" To: "Andrey Jr. Melnikov" Cc: linux-kernel@vger.kernel.org, linux-ext4@vger.kernel.org Subject: Re: ext4 file system corruption with v4.19.3 / v4.19.4 Message-ID: <20181128041555.GE31885@thunk.org> Mail-Followup-To: "Theodore Y. Ts'o" , "Andrey Jr. Melnikov" , linux-kernel@vger.kernel.org, linux-ext4@vger.kernel.org References: <065643a0-f9aa-a361-715a-03ca978d9228@roeck-us.net> MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: User-Agent: Mutt/1.10.1 (2018-07-13) X-SA-Exim-Connect-IP: X-SA-Exim-Mail-From: tytso@thunk.org X-SA-Exim-Scanned: No (on imap.thunk.org); SAEximRunCond expanded to false Sender: linux-kernel-owner@vger.kernel.org Precedence: bulk List-ID: X-Mailing-List: linux-kernel@vger.kernel.org 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? 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.) (b) What hardware are you using? (SSD? SATA-attached? NVMe-attached?) (c) Are you using LVM? LUKS (e.g., disk encrypted)? (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.) - Ted