From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S1753669AbdADGAK (ORCPT ); Wed, 4 Jan 2017 01:00:10 -0500 Received: from hr2.samba.org ([144.76.82.148]:28550 "EHLO hr2.samba.org" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1752282AbdADGAI (ORCPT ); Wed, 4 Jan 2017 01:00:08 -0500 Date: Wed, 4 Jan 2017 16:18:08 +1100 From: Anton Blanchard To: jack@suse.cz, Michael Ellerman , Benjamin Herrenschmidt , Paul Mackerras , Stephen Rothwell , axboe@fb.com Cc: linuxppc-dev@lists.ozlabs.org, linux-kernel@vger.kernel.org, linux-ext4@vger.kernel.org, linux-fsdevel@vger.kernel.org Subject: ext4 filesystem corruption with 4.10-rc2 on ppc64le Message-ID: <20170104161808.5ad7b4fd@kryten> X-Mailer: Claws Mail 3.13.2 (GTK+ 2.24.30; x86_64-pc-linux-gnu) MIME-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: 7bit Sender: linux-kernel-owner@vger.kernel.org List-ID: X-Mailing-List: linux-kernel@vger.kernel.org Hi, I'm consistently seeing ext4 filesystem corruption using a mainline kernel. It doesn't take much to trigger it - download a ppc64le Ubuntu cloud image, boot it in KVM and run: sudo apt-get update sudo apt-get dist-upgrade sudo reboot And it never makes it back up, dying with rather severe filesystem corruption. I've narrowed it down to: 64e1c57fa474 ("ext4: Use clean_bdev_aliases() instead of iteration") e64855c6cfaa ("fs: Add helper to clean bdev aliases under a bh and use it") ce98321bf7d2 ("fs: Remove unmap_underlying_metadata") Backing these patches out fixes the issue. Anton