From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S1755379Ab1LFWcN (ORCPT ); Tue, 6 Dec 2011 17:32:13 -0500 Received: from mail-qy0-f174.google.com ([209.85.216.174]:33197 "EHLO mail-qy0-f174.google.com" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1753421Ab1LFWcM (ORCPT ); Tue, 6 Dec 2011 17:32:12 -0500 Date: Tue, 6 Dec 2011 14:31:37 -0800 (PST) From: Hugh Dickins X-X-Sender: hugh@sister.anvils To: Yongqiang Yang cc: Allison Henderson , "Ted Ts'o" , Curt Wohlgemuth , Surbhi Palande , Rafael Wysocki , linux-ext4@vger.kernel.org, linux-kernel@vger.kernel.org Subject: Re: Bug with "fix partial page writes" [3.2-rc regression] In-Reply-To: Message-ID: References: <20111121165626.GD14568@thunk.org> <4EDD729E.2060402@linux.vnet.ibm.com> User-Agent: Alpine 2.00 (LSU 1167 2008-08-23) MIME-Version: 1.0 Content-Type: MULTIPART/MIXED; BOUNDARY="8323584-813777252-1323210711=:1949" Sender: linux-kernel-owner@vger.kernel.org List-ID: X-Mailing-List: linux-kernel@vger.kernel.org This message is in MIME format. The first part should be readable text, while the remaining parts are likely unreadable without MIME-aware tools. --8323584-813777252-1323210711=:1949 Content-Type: TEXT/PLAIN; charset=ISO-8859-1 Content-Transfer-Encoding: QUOTED-PRINTABLE On Tue, 6 Dec 2011, Yongqiang Yang wrote: > On Tue, Dec 6, 2011 at 4:55 PM, Hugh Dickins wrote: > > > > I've now tried the fsx test on three machines, with both 1/2 and 2/2 > > applied to 3.2-rc4. =A0On one machine, with ext2 on loop on tmpfs, the > > fsx test failed in a couple of minutes with those patches; on another > > machine, with ext2 on loop on tmpfs, it failed after about 40 minutes > > with =A0the patches; on this laptop, with ext2 on SSD, it's just now > > failed after 35 minutes with the patches. > ext2? So files are indirect mapped? If so, the failure should has > nothing to do with punching hole, I remember that punch hole is not > supported for indirect mapped files. Yes, I am not trying to test hole punching: just trying to do my own testing under traditional loads, and hitting problems in changes which have gone into extN to fix up hole punching. Some of the time I've been using an old fsx which doesn't even know about fallocate(), some of the time a recent fsx from xfstests. Most of the time I've been using ext2, but occasionally I try it on ext4. I think the only thing which makes the problems go away is blocksize same as pagesize; but it's a long time since I tried nomblk_io_submit, that made a big difference around 2.6.38/39, perhaps it still does. >=20 > Do you mean fsx failure or the bug you reported earlier due to > referencing a unlocked page? In first quoted paragraph above, fsx failure. Hugh --8323584-813777252-1323210711=:1949--