From: Chandan Rajendra <chandan@linux.vnet.ibm.com>
To: Anton Blanchard <anton@samba.org>
Cc: jack@suse.cz, Michael Ellerman <mpe@ellerman.id.au>,
Benjamin Herrenschmidt <benh@kernel.crashing.org>,
Paul Mackerras <paulus@samba.org>,
Stephen Rothwell <sfr@canb.auug.org.au>,
axboe@fb.com, linuxppc-dev@lists.ozlabs.org,
linux-kernel@vger.kernel.org, linux-ext4@vger.kernel.org,
linux-fsdevel@vger.kernel.org
Subject: Re: ext4 filesystem corruption with 4.10-rc2 on ppc64le
Date: Wed, 04 Jan 2017 11:32:42 +0530 [thread overview]
Message-ID: <6085340.JSrffQ0Szo@localhost.localdomain> (raw)
In-Reply-To: <20170104161808.5ad7b4fd@kryten>
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@vger.kernel.org
> More majordomo info at http://vger.kernel.org/majordomo-info.html
>
--
chandan
next prev parent reply other threads:[~2017-01-04 7:37 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-01-04 5:18 ext4 filesystem corruption with 4.10-rc2 on ppc64le Anton Blanchard
2017-01-04 6:02 ` Chandan Rajendra [this message]
2017-01-04 15:28 ` Theodore Ts'o
2017-01-04 16:23 ` Jens Axboe
2017-01-04 18:09 ` Linus Torvalds
2017-01-05 10:44 ` Anton Blanchard
2017-01-09 4:10 ` Chandan Rajendra
2017-01-04 7:34 ` luigi burdo
2017-01-04 15:09 ` Jens Axboe
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=6085340.JSrffQ0Szo@localhost.localdomain \
--to=chandan@linux.vnet.ibm.com \
--cc=anton@samba.org \
--cc=axboe@fb.com \
--cc=benh@kernel.crashing.org \
--cc=jack@suse.cz \
--cc=linux-ext4@vger.kernel.org \
--cc=linux-fsdevel@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linuxppc-dev@lists.ozlabs.org \
--cc=mpe@ellerman.id.au \
--cc=paulus@samba.org \
--cc=sfr@canb.auug.org.au \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).