From: "Aneesh Kumar K.V" <aneesh.kumar@linux.vnet.ibm.com>
Subject: Re: BUG: soft lockup - CPU#0 stuck for 11s! [fsstress:5534]
Date: Fri, 21 Dec 2007 16:28:56 +0530
Message-ID: <20071221105856.GA6989@skywalker>
References: <20071220143242.GB6953@skywalker>
Mime-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Cc: Theodore Tso <tytso@mit.edu>, Andreas Dilger <adilger@sun.com>,
	Alex Tomas <bzzz@sun.com>
To: ext4 development <linux-ext4@vger.kernel.org>
Content-Disposition: inline
In-Reply-To: <20071220143242.GB6953@skywalker>
Sender: linux-ext4-owner@vger.kernel.org

On Thu, Dec 20, 2007 at 08:02:42PM +0530, Aneesh Kumar K.V wrote:
> I am seeing this with the patch queue. I can reproduce this on x86 and
> powerpc. I see the file system full when this happens. The same happens even
> without delalloc enabled.
> 
> 


The below patch fix the same for me. One thing i observed with the patch queue
is, enabling delalloc by default. Delalloc doesn't handle the file system full
case because there is no block reservation. Unless we have block reservation i
guess we should disable delalloc by default.

I will send a full patch with proper log message.

diff --git a/fs/ext4/mballoc.c b/fs/ext4/mballoc.c
index 72e1920..8b45ac0 100644
--- a/fs/ext4/mballoc.c
+++ b/fs/ext4/mballoc.c
@@ -3791,6 +3791,7 @@ repeat:
 	/* if we still need more blocks and some PAs were used, try again */
 	if (free < needed && busy) {
 		ext4_unlock_group(sb, group);
+		schedule_timeout(HZ);
 		goto repeat;
 	}