[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-Id: <6085340.JSrffQ0Szo@localhost.localdomain>
Date: Wed, 04 Jan 2017 11:32:42 +0530
From: Chandan Rajendra <chandan@...ux.vnet.ibm.com>
To: Anton Blanchard <anton@...ba.org>
Cc: jack@...e.cz, Michael Ellerman <mpe@...erman.id.au>,
Benjamin Herrenschmidt <benh@...nel.crashing.org>,
Paul Mackerras <paulus@...ba.org>,
Stephen Rothwell <sfr@...b.auug.org.au>, axboe@...com,
linuxppc-dev@...ts.ozlabs.org, linux-kernel@...r.kernel.org,
linux-ext4@...r.kernel.org, linux-fsdevel@...r.kernel.org
Subject: Re: ext4 filesystem corruption with 4.10-rc2 on ppc64le
On Wednesday, January 04, 2017 04:18:08 PM Anton Blanchard wrote:
> 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.
Hi,
The patch at https://patchwork.kernel.org/patch/9488235/ should fix the
bug.
>
> 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
> --
> To unsubscribe from this list: send the line "unsubscribe linux-ext4" in
> the body of a message to majordomo@...r.kernel.org
> More majordomo info at http://vger.kernel.org/majordomo-info.html
>
--
chandan
Powered by blists - more mailing lists