From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S1033890AbdAIEKv (ORCPT ); Sun, 8 Jan 2017 23:10:51 -0500 Received: from mx0b-001b2d01.pphosted.com ([148.163.158.5]:55722 "EHLO mx0a-001b2d01.pphosted.com" rhost-flags-OK-OK-OK-FAIL) by vger.kernel.org with ESMTP id S1758794AbdAIEKt (ORCPT ); Sun, 8 Jan 2017 23:10:49 -0500 From: Chandan Rajendra To: "Theodore Ts'o" Cc: Anton Blanchard , jack@suse.cz, Michael Ellerman , Benjamin Herrenschmidt , Paul Mackerras , Stephen Rothwell , axboe@fb.com, linuxppc-dev@lists.ozlabs.org, linux-kernel@vger.kernel.org, linux-ext4@vger.kernel.org, linux-fsdevel@vger.kernel.org, Jens Axboe , torvalds@linux-foundation.org Subject: Re: ext4 filesystem corruption with 4.10-rc2 on ppc64le Date: Mon, 09 Jan 2017 09:40:29 +0530 User-Agent: KMail/4.14.10 (Linux/4.8.13-100.fc23.x86_64; KDE/4.14.20; x86_64; ; ) In-Reply-To: <20170104152837.wdh7cdncs7gyged7@thunk.org> References: <20170104161808.5ad7b4fd@kryten> <6085340.JSrffQ0Szo@localhost.localdomain> <20170104152837.wdh7cdncs7gyged7@thunk.org> MIME-Version: 1.0 Content-Transfer-Encoding: 7Bit Content-Type: text/plain; charset="us-ascii" X-TM-AS-MML: disable X-Content-Scanned: Fidelis XPS MAILER x-cbid: 17010904-0008-0000-0000-000000FA6F3F X-IBM-AV-DETECTION: SAVI=unused REMOTE=unused XFE=unused x-cbparentid: 17010904-0009-0000-0000-000008D79765 Message-Id: <14716846.DtMXVimRBg@localhost.localdomain> X-Proofpoint-Virus-Version: vendor=fsecure engine=2.50.10432:,, definitions=2017-01-08_20:,, signatures=0 X-Proofpoint-Spam-Details: rule=outbound_notspam policy=outbound score=0 spamscore=0 suspectscore=3 malwarescore=0 phishscore=0 adultscore=0 bulkscore=0 classifier=spam adjust=0 reason=mlx scancount=1 engine=8.0.1-1612050000 definitions=main-1701090065 Sender: linux-kernel-owner@vger.kernel.org List-ID: X-Mailing-List: linux-kernel@vger.kernel.org On Wednesday, January 04, 2017 10:28:37 AM Theodore Ts'o wrote: > On Wed, Jan 04, 2017 at 11:32:42AM +0530, Chandan Rajendra wrote: > > On Wednesday, January 04, 2017 04:18:08 PM Anton Blanchard wrote: > > > 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. > > > > The patch at https://patchwork.kernel.org/patch/9488235/ should fix the > > bug. > > It looks like this patch is already queued up on the "for-linus" > branch on the linux-block.git tree. > > Chandra, thanks for pointing this out! I had missed your e-mail from > Christmas day, and it was on my todo list to figure out why I was > seeing lots of 1k block regressions on gce-xfstests post-merge window > that wasn't showing up on the ext4.git tree before I sent my pull > request to Linus. > > Jens, could you expedite a pull request to Linus? This is affecting > ext4 on 1k block file systems on x86/x86_64, so this is not a ppc-only > regression. > > Anton or Chandan, could you do me a favor and verify whether or not > 64k block sizes are working for you on ppcle on ext4 by running > xfstests? Light duty testing works for me but when I stress ext4 with > pagesize==blocksize on ppcle64 via xfstests, it blows up. I suspect > (but am not sure) it's due to (non-upstream) device driver issues, and > a verification that you can run xfstests on your ppcle64 systems using > standard upstream device drivers would be very helpful, since I don't > have easy console access on the machines I have access to at $WORK. :-( Hi Ted, I found one regression w.r.t 64k blocksize. I posted a patch (http://marc.info/?l=linux-block&m=148388687722745&w=2) to fix the issue. -- chandan