From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S1753453AbZBQRVp (ORCPT ); Tue, 17 Feb 2009 12:21:45 -0500 Received: (majordomo@vger.kernel.org) by vger.kernel.org id S1752478AbZBQRVg (ORCPT ); Tue, 17 Feb 2009 12:21:36 -0500 Received: from sov-mail-b0016.gradwell.net ([193.84.87.40]:44971 "EHLO sov-mail-b0016.gradwell.net" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1752195AbZBQRVg (ORCPT ); Tue, 17 Feb 2009 12:21:36 -0500 Date: Tue, 17 Feb 2009 17:21:15 +0000 From: Alex Buell To: Theodore Tso Cc: Andres Freund , adilger@sun.com, LKML , linux-ext4@vger.kernel.org, Jonathan Bastien-Filiatrault , "Aneesh Kumar K.V" Subject: Re: EXT4 ENOSPC Bug Message-ID: <20090217172115.7a42044a@lithium.local.net> In-Reply-To: <20090216190001.GB11788@mini-me.lan> References: <20090216162028.3032666a@lithium.local.net> <200811291418.24672.andres@anarazel.de> <200812100108.04163.andres@anarazel.de> <49994FEF.2020908@anarazel.de> <20090216150156.GD22619@mini-me.lan> <499985C7.8010302@anarazel.de> <20090216190001.GB11788@mini-me.lan> Organization: One tortoiseshell cat, very high maintenance X-Mailer: Claws Mail 3.7.0 (GTK+ 2.12.11; i686-pc-linux-gnu) X-Face: "wUuhsy:X)M;>-dA\j"&y@*\$91]iX10Iv1WG_oNbGYpo,eqc06O?"VSeRTx]xM\LiITUh01z}<|GF/4Gzz(MAU~;p4AS,%TB69M:vB-9+i'#W7$UQCW&UP#zt{VdLlzEiw8k~jL< 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 On Mon, 16 Feb 2009 14:00:01 -0500, I waved a wand and this message magically appears in front of Theodore Tso: > On Mon, Feb 16, 2009 at 04:27:03PM +0100, Andres Freund wrote: > > > > So, yes, seems to be an inode allocation problem. > > Andres, Alex, others, > > I'm pretty sure the ENOSPC problem which you both found is an inode > allocation problem. Some of you seem to have an easier time > reproducing it than others; could you try this patch, and periodically > scan your system logs for the message "ext4: find_group_flex failed, > fallback succeeded"? If the problem goes away for you, and you find > the occasional aforemention message in your system log, that will > confirm what I suspect, which is the bug is in fs/ext4/inode.c's > find_group_flex() function. (If I'm wrong, the fallback code will > activate only when the filesystem is genuinely out of inodes, which > should be very rare.) OK, I had to go look through the archives on linux-ext4 mailing list to see what the context was. For myself, this used to happen at least once a week with 2.6.26, and less frequently with 2.6.27. I think that 2.6.28 with your patch should get rid of that problem altogether. I will of course get in touch should I see any more of these find_group_flex failures as that would mean your patch worked. Thanks for your work on tracking this one down! -- http://www.munted.org.uk Fearsome grindings.