From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: from relay.sgi.com (relay1.corp.sgi.com [137.38.102.111]) by oss.sgi.com (8.14.3/8.14.3/SuSE Linux 0.8) with ESMTP id q3NHwx91222129 for ; Mon, 23 Apr 2012 12:58:59 -0500 Date: Mon, 23 Apr 2012 13:01:23 -0500 From: Ben Myers Subject: Re: [PATCH 00/37] xfs: current 3.4 patch queue Message-ID: <20120423180123.GH16881@sgi.com> References: <1335160747-17254-1-git-send-email-david@fromorbit.com> MIME-Version: 1.0 Content-Disposition: inline In-Reply-To: <1335160747-17254-1-git-send-email-david@fromorbit.com> List-Id: XFS Filesystem from SGI List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , Content-Type: text/plain; charset="us-ascii" Content-Transfer-Encoding: 7bit Sender: xfs-bounces@oss.sgi.com Errors-To: xfs-bounces@oss.sgi.com To: Dave Chinner Cc: xfs@oss.sgi.com Hi Dave, On Mon, Apr 23, 2012 at 03:58:30PM +1000, Dave Chinner wrote: > I haven't been able to reproduce Ben's CIL commit > sequence assert failure from the async log flushing patch (patch > 12/37), so whatever the cause of that problem is is still unknown. > > [ Actually, as I wrote this I had a concurrent rm -rf just trip this > assert, so the problem is real and I've obviously got more work to > do on this one.... ] I just hit it again, looks like in test 273. [ 6587.548841] XFS: Assertion failed: push_seq > 0 && push_seq <= ctx->sequence, file: /root/xfs/fs/xfs/xfs_log_cil.c, line: 405 This time I have a dump. ;) -Ben _______________________________________________ xfs mailing list xfs@oss.sgi.com http://oss.sgi.com/mailman/listinfo/xfs