Received: by 2002:ad5:474a:0:0:0:0:0 with SMTP id i10csp60074imu; Tue, 27 Nov 2018 07:50:22 -0800 (PST) X-Google-Smtp-Source: AFSGD/X84SDv3aVNVSOHe52RMRg0v4wqPgE3xcVisArT67VC3XprDY6j5z7AdfA2kqYoczELUUK3 X-Received: by 2002:a63:295:: with SMTP id 143mr28665262pgc.362.1543333822619; Tue, 27 Nov 2018 07:50:22 -0800 (PST) ARC-Seal: i=1; a=rsa-sha256; t=1543333822; cv=none; d=google.com; s=arc-20160816; b=ZfzpM+eDOCS2fFzqyoxj82LomXFF/tElGz7ZUKc8eEB12H5mH1PX4jQ9RRSolY1RcI nuKLbih29uXpjqwuNsqMRiPZMo0YndTwIXckzl/hVoq2gjXaY/RWMS9LIoQmXfmTG+QI MPhpDIK3F4moxU3ZSDV6kc/uFvtCgqIFI1VKQIguTZsA7yqB7WOlYkUojammQaBSt0K4 Ko2+VPAP4iKkQk625l/uz5JmkXkJAdBHk2GWOz+fjNM+SD5F17Qw23ECQqHyLVs2qTlc ZY+1Nyc5FQwOk0l87UG3fbFiKiF8sJWh1b2HAa92o9hMlWIf98qaMZaAZD8uAvl40Eko NtgA== ARC-Message-Signature: i=1; a=rsa-sha256; c=relaxed/relaxed; d=google.com; s=arc-20160816; h=list-id:precedence:sender:mime-version:references:in-reply-to :message-id:date:subject:cc:to:from:dkim-signature; bh=uYx0h1BvR80PmLMCgYfASPTxMfp9MTQuCRXFonzusP8=; b=xdQLLvU55eQVJFRaIJtPkGvwJOD84C2PwByJlEB8w6kDH+HvDc25LUdp9e5SJeo/3d /zRQXojlL4vjegpmB2geHeTlO74yY0AdQv+NIJ6Gvy6ajSoyrNdcUyb5t1eIrYLp9KEL klcjxhwBwYOR3dNsifD0E6+XKK5s6CaGU0aa4UBhPPWvpQIqTJoF52CfSOs5EXxa94DN YyfHrx3uGDg3xeSUAvDryy3VQTrBW0fBPaT91ZA/+kSPk3sWWRbLKUtdZRRQinfqFmvW hZs2afQsR72L/khTO87WH33WYYcAg/EYxBbr9Y0fxjOGFqGGvZF7a19+R5Gq6L1dP5PS wUlw== ARC-Authentication-Results: i=1; mx.google.com; dkim=pass header.i=@mailbox.org header.s=mail20150812 header.b=Jhj+Ywxx; 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; dmarc=pass (p=NONE sp=NONE dis=NONE) header.from=mailbox.org Return-Path: Received: from vger.kernel.org (vger.kernel.org. [209.132.180.67]) by mx.google.com with ESMTP id 33si4287418plu.169.2018.11.27.07.49.47; Tue, 27 Nov 2018 07:50:22 -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=pass header.i=@mailbox.org header.s=mail20150812 header.b=Jhj+Ywxx; 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; dmarc=pass (p=NONE sp=NONE dis=NONE) header.from=mailbox.org Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S1729934AbeK1Cqq (ORCPT + 99 others); Tue, 27 Nov 2018 21:46:46 -0500 Received: from mx2.mailbox.org ([80.241.60.215]:11418 "EHLO mx2.mailbox.org" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1729553AbeK1Cqq (ORCPT ); Tue, 27 Nov 2018 21:46:46 -0500 Received: from smtp2.mailbox.org (unknown [IPv6:2001:67c:2050:105:465:1:2:0]) (using TLSv1.2 with cipher ECDHE-RSA-CHACHA20-POLY1305 (256/256 bits)) (No client certificate requested) by mx2.mailbox.org (Postfix) with ESMTPS id AA66BA1481; Tue, 27 Nov 2018 16:48:24 +0100 (CET) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/simple; d=mailbox.org; h= content-type:content-type:mime-version:references:in-reply-to :message-id:date:date:subject:subject:from:from:received; s= mail20150812; t=1543333703; bh=uYx0h1BvR80PmLMCgYfASPTxMfp9MTQuC RXFonzusP8=; b=Jhj+YwxxymuBjXJaWBmTOjY6pi5A8TFcfXS4UdOWtQfh00xlh zp3e59VqCF+O+QLDHIxHK0MPiyBa84TIuvLod7O7fyQ+OjuN2h3R4kwnJBmv80TH cUOKzxLHwEKt9GkM2wQ5lUNlnXzID85niiRfKZvzZU5awmSDXKd5iyTI9+meYeDQ IRo/1pE5TR1otbp/cDBLPz20rHAobSVWtnYHu2C8nerow1HsViumgy9ukVFZHv+m VltLf0vN2IMZbj5wj6lN1M1frkcX5usfzKcL0FU88hVd4CDPNqadSI9ImMKp9xll S+f1dOgb2DDDmhjjQQzhTxji8//iJFOXu8ocA== X-Virus-Scanned: amavisd-new at heinlein-support.de Received: from smtp2.mailbox.org ([80.241.60.241]) by spamfilter04.heinlein-hosting.de (spamfilter04.heinlein-hosting.de [80.241.56.122]) (amavisd-new, port 10030) with ESMTP id fU2u_60h8QfZ; Tue, 27 Nov 2018 16:48:23 +0100 (CET) From: Rainer Fiebig To: linux-kernel@vger.kernel.org Cc: Guenter Roeck , Theodore Ts'o , Andreas Dilger , linux-ext4@vger.kernel.org Subject: Re: ext4 file system corruption with v4.19.3 / v4.19.4 Date: Tue, 27 Nov 2018 16:50:05 +0100 Message-ID: <2469172.LfQfxQsF9r@siriux> In-Reply-To: References: <065643a0-f9aa-a361-715a-03ca978d9228@roeck-us.net> MIME-Version: 1.0 Content-Type: multipart/signed; boundary="nextPart2634171.pyS62653GN"; micalg="pgp-sha256"; protocol="application/pgp-signature" Sender: linux-kernel-owner@vger.kernel.org Precedence: bulk List-ID: X-Mailing-List: linux-kernel@vger.kernel.org --nextPart2634171.pyS62653GN Content-Transfer-Encoding: quoted-printable Content-Type: text/plain; charset="us-ascii" Am Dienstag, 27. November 2018, 06:32:08 schrieb Guenter Roeck: > [trying again, this time with correct kernel.org address] >=20 > Hi, >=20 > I have seen the following and similar problems several times, > with both v4.19.3 and v4.19.4: >=20 > Nov 23 04:32:25 mars kernel: [112668.673671] EXT4-fs error (device sd= b1): > ext4_iget:4831: inode #12602889: comm git: bad extra_isize 33661 (ino= de > size 256) Nov 23 04:32:25 mars kernel: [112668.675217] Aborting journ= al on > device sdb1-8. Nov 23 04:32:25 mars kernel: [112668.676681] EXT4-fs (= sdb1): > Remounting filesystem read-only Nov 23 04:32:25 mars kernel: > [112668.808886] EXT4-fs error (device sdb1): ext4_iget:4831: inode > #12602881: comm rm: bad extra_isize 33685 (inode size 256) ... >=20 > Nov 25 00:12:43 saturn kernel: [59377.725984] EXT4-fs error (device s= da1): > ext4_lookup:1578: inode #238034131: comm updatedb.mlocat: deleted ino= de > referenced: 238160407 Nov 25 00:12:43 saturn kernel: [59377.766638] > Aborting journal on device sda1-8. Nov 25 00:12:43 saturn kernel: > [59377.779372] EXT4-fs (sda1): Remounting filesystem read-only ... >=20 > Nov 24 01:52:31 saturn kernel: [189085.240016] EXT4-fs error (device = sda1): > ext4_lookup:1578: inode #52038457: comm nfsd: deleted inode reference= d: > 52043796 Nov 24 01:52:31 saturn kernel: [189085.263427] Aborting jour= nal on > device sda1-8. Nov 24 01:52:31 saturn kernel: [189085.275313] EXT4-fs= > (sda1): Remounting filesystem read-only >=20 >=20 > The same systems running v4.18.6 never experienced a problem. >=20 > Has anyone else seen similar problems ? Is there anything I can do > to help tracking down the problem ? >=20 > Thanks, > Guenter This is already being discussed here:=20 https://bugzilla.kernel.org/show_bug.cgi?id=3D201685 I guess bisecting between 4.18.0 and 4.19.0 by someone who is proficien= t in=20 this and is affected by the problem would be immensely valuable. I'm not affected and am a bit reluctant to expose my production system = to=20 this. ;) So long! Rainer Fiebig=20 =2D-=20 The truth always turns out to be simpler than you thought. Richard Feynman --nextPart2634171.pyS62653GN Content-Type: application/pgp-signature; name="signature.asc" Content-Description: This is a digitally signed message part. Content-Transfer-Encoding: 7Bit -----BEGIN PGP SIGNATURE----- iQIzBAABCAAdFiEE6yx5PjBNuGB2qJXG8OH3JiWK+PUFAlv9Z60ACgkQ8OH3JiWK +PWDOQ/9EjNDKB9iogBOWd4TT0W5UWpZELT3m6sGr8pThX4lbDTmQaYgu+dqbrvB VNye9KBBthDeJurSZN5VJLlSZ+fcwzUfBPBAq3EfLPB0pfHrB/m6fJtAc0AyEjPT sZ3JE/jTMCYsh/r1rLYHHkBHwiPJ3l/+f5aUZu2KuqGGmw4Ff8FYCy6JeBFafBSS 3obyzPJSKycwihXc5W0gA3TNdvF6JTWnC8ji9TEo1l5Gc3TzoWJEs4Ody3z4EQUn KQ+/o0e7+KC58tgT2x9SrARQ0UmpGXAWLogKAWUZfsuoHQoIYyUiuJ5ODHbBcSUh b98vIBnWyFQLmFxXiPvPnvWiVlfsagMKrUdR+xYugUvve5Q6vIUmkQHsUjijIlhC lpbdoc+qV648XfNPLs6hiNmv1oYLdwtP/JreLaTbNzD+eD1+D3m8TI7C+9qF9tJG dtUxOjt4LM6Mbc7aQ5p9MJa+uTY9Ufi7juMl795/yeGahTJvIw8t76Ki2cBXXm5K PXx7kN9k8Cr3pUIjVun6iSM+iSUhul10sZhNT+cwsiA8hos9GE5+bene1wSOxUQb GoedusqHpQz1/p+TTQxhNR98V3fJatKxhZKRX3mLWhO6TJ369dB6PMD68kYjcx8p v33hmANDrg3hhMfaJkJ915s4zHhY1n3i0C5ZJ1OGCWNYEboAgio= =crZc -----END PGP SIGNATURE----- --nextPart2634171.pyS62653GN--