From mboxrd@z Thu Jan 1 00:00:00 1970 From: Dave Chinner Subject: Re: [PATCH 00/10] dcache cleanups Date: Wed, 13 Oct 2010 12:46:02 +1100 Message-ID: <20101013014601.GT4681@dastard> References: <20101010093620.416498597@canuck.infradead.org> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Cc: viro@zeniv.linux.org.uk, eparis@redhat.com, linux-fsdevel@vger.kernel.org To: Christoph Hellwig Return-path: Received: from bld-mail16.adl2.internode.on.net ([150.101.137.101]:59777 "EHLO mail.internode.on.net" rhost-flags-OK-OK-OK-FAIL) by vger.kernel.org with ESMTP id S1751370Ab0JMBqG (ORCPT ); Tue, 12 Oct 2010 21:46:06 -0400 Content-Disposition: inline In-Reply-To: <20101010093620.416498597@canuck.infradead.org> Sender: linux-fsdevel-owner@vger.kernel.org List-ID: On Sun, Oct 10, 2010 at 05:36:20AM -0400, Christoph Hellwig wrote: > A couple of dcache cleanups in preparation of the dcache_lock splitup. > Note that I already sent the first patch individually, but this series > contains a fixed version. Something in this series causes xfsdump to get really unhappy (xfstests 026) - probably the get_parent changes. This message is just continually spewed and the xfsdump process cannot be killed: [ 884.392813] export: Eeek filesystem root is not connected, impossible [ 884.393873] export: Eeek filesystem root is not connected, impossible [ 884.394669] export: Eeek filesystem root is not connected, impossible [ 884.395648] export: Eeek filesystem root is not connected, impossible [ 884.396482] export: Eeek filesystem root is not connected, impossible [ 884.397487] export: Eeek filesystem root is not connected, impossible [ 884.398241] export: Eeek filesystem root is not connected, impossible [ 884.399036] export: Eeek filesystem root is not connected, impossible [ 884.400148] export: Eeek filesystem root is not connected, impossible [ 884.401186] export: Eeek filesystem root is not connected, impossible Cheers, Dave. -- Dave Chinner david@fromorbit.com