All of lore.kernel.org
 help / color / mirror / Atom feed
From: Theodore Tso <tytso@mit.edu>
To: Andres Freund <andres@anarazel.de>
Cc: Alex Buell <alex.buell@munted.org.uk>,
	adilger@sun.com, LKML <linux-kernel@vger.kernel.org>,
	linux-ext4@vger.kernel.org,
	Jonathan Bastien-Filiatrault <joe@x2a.org>,
	"Aneesh Kumar K.V" <aneesh.kumar@linux.vnet.ibm.com>
Subject: Re: EXT4 ENOSPC Bug
Date: Wed, 18 Feb 2009 16:29:57 -0500	[thread overview]
Message-ID: <20090218212957.GR3600@mini-me.lan> (raw)
In-Reply-To: <499C7B41.1090800@anarazel.de>

On Wed, Feb 18, 2009 at 10:18:57PM +0100, Andres Freund wrote:
> On one of the machines I got several thousand of:
>
> [10379.575904] ext4: find_group_flex failed, fallback succeeded dir 416319
> [10379.576002] ext4: find_group_flex failed, fallback succeeded dir 416319
> [10379.579981] ext4: find_group_flex failed, fallback succeeded dir 416319
> [10379.580097] ext4: find_group_flex failed, fallback succeeded dir 416319
> (with different directories)

Ok, that's good.  Good to know the workaround works.  

Can you send me a dumpe2fs of the filesystem in question?  I'm curious
what was going on...

> No userspace visible behaviour.
>
> So it seems you were right. It seems sensible to put that patch without  
> printk in the kernel until the issue is fully solved...

Thanks for the report.  I'll push the workaround patch to Linus for
2.6.29 to avoid this problem for now.  I recently sent to linux-ext4
for comment a patch to revamp the Orlov allocator for flex_bg and to
use that instead of find_group_flex(), but no way that's going into
2.6.29 at this point....

							- Ted

  reply	other threads:[~2009-02-18 22:48 UTC|newest]

Thread overview: 47+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2008-11-29 13:18 EXT4 ENOSPC Bug Andres Freund
2008-11-29 20:32 ` Jonathan Bastien-Filiatrault
2008-11-29 21:15 ` Theodore Tso
2008-11-29 21:31   ` Andres Freund
2008-12-01 12:34 ` Andres Freund
2008-12-01 19:42   ` Andreas Dilger
2008-12-01 20:16     ` Andres Freund
2008-12-02  7:57       ` Theodore Tso
2008-12-02 14:58         ` Andres Freund
2008-12-02 16:47           ` Theodore Tso
2008-12-02 17:47             ` Andres Freund
2008-12-02 20:33               ` Theodore Tso
2008-12-03  0:37                 ` Jonathan Bastien-Filiatrault
2008-12-03  0:40                   ` Jonathan Bastien-Filiatrault
2008-12-03  4:37                     ` Theodore Tso
2008-12-03 15:34                   ` Aneesh Kumar K.V
2008-12-03 17:23                     ` Theodore Tso
2008-12-03 18:18                       ` Andres Freund
2008-12-02 15:26     ` Henrique de Moraes Holschuh
2008-12-10  0:07 ` Andres Freund
2009-02-16 11:37   ` Andres Freund
2009-02-16 15:01     ` Theodore Tso
2009-02-16 15:27       ` Andres Freund
2009-02-16 15:27         ` Andres Freund
2009-02-16 19:00         ` Theodore Tso
2009-02-17 17:21           ` Alex Buell
2009-02-17 17:36           ` Andres Freund
2009-02-17 17:36             ` Andres Freund
2009-02-18 21:18             ` Andres Freund
2009-02-18 21:18               ` Andres Freund
2009-02-18 21:29               ` Theodore Tso [this message]
2009-02-19  2:18                 ` Andres Freund
2009-02-19  2:18                   ` Andres Freund
2009-02-19  3:22                   ` Theodore Tso
2009-02-19 15:46                     ` Eric Sandeen
2009-02-19 15:46                       ` Eric Sandeen
2009-02-23  2:02                       ` Theodore Tso
2009-02-27  3:57                 ` Andres Freund
2009-02-27  3:57                   ` Andres Freund
2009-02-17 18:13           ` Eric Sandeen
2009-02-17 18:13             ` Eric Sandeen
2009-02-17 20:08             ` Eric Sandeen
2009-02-17 20:08             ` Eric Sandeen
2009-02-17 22:00               ` Theodore Tso
2009-02-17 22:30               ` Alex Buell
2009-02-17 22:56                 ` Eric Sandeen
2009-02-17 22:59                   ` Alex Buell

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=20090218212957.GR3600@mini-me.lan \
    --to=tytso@mit.edu \
    --cc=adilger@sun.com \
    --cc=alex.buell@munted.org.uk \
    --cc=andres@anarazel.de \
    --cc=aneesh.kumar@linux.vnet.ibm.com \
    --cc=joe@x2a.org \
    --cc=linux-ext4@vger.kernel.org \
    --cc=linux-kernel@vger.kernel.org \
    /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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.