From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: from mail.wl.linuxfoundation.org ([198.145.29.98]:35692 "EHLO mail.wl.linuxfoundation.org" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1733280AbeKWKoD (ORCPT ); Fri, 23 Nov 2018 05:44:03 -0500 Received: from mail.wl.linuxfoundation.org (localhost [127.0.0.1]) by mail.wl.linuxfoundation.org (Postfix) with ESMTP id 95A6B2C77D for ; Fri, 23 Nov 2018 00:02:12 +0000 (UTC) From: bugzilla-daemon@bugzilla.kernel.org To: linux-ext4@vger.kernel.org Subject: [Bug 201685] ext4 file system corruption Date: Fri, 23 Nov 2018 00:02:13 +0000 Message-ID: In-Reply-To: References: Content-Type: text/plain; charset="UTF-8" Content-Transfer-Encoding: 8BIT MIME-Version: 1.0 Sender: linux-ext4-owner@vger.kernel.org List-ID: https://bugzilla.kernel.org/show_bug.cgi?id=201685 --- Comment #37 from Jimmy.Jazz@gmx.net --- @Jen Axboe please read worth not worse in comment 33 I tried your patch for 4.19.3 and still get quite harmful ext4 errors like this one, EXT4-fs error (device dm-4): ext4_xattr_ibody_get:592: inode #4881425: comm rsync: corrupted in-inode xattr The filesystems were clean at boot time and the system was idle. tune2fs ends with FS Error count: 64 First error time: Fri Nov 23 00:19:25 2018 First error function: ext4_xattr_ibody_get First error line #: 592 First error inode #: 4881425 First error block #: 0 Last error time: Fri Nov 23 00:19:25 2018 Last error function: ext4_xattr_ibody_get Last error line #: 592 Last error inode #: 4881430 Last error block #: 0 MMP block number: 9255 MMP update interval: 5 If you are interested in its dumpe2fs result let me know. I don't use binary modules. -- You are receiving this mail because: You are watching the assignee of the bug.