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@xxxxxxxxxxxxx -- To unsubscribe from this list: send the line "unsubscribe linux-fsdevel" in the body of a message to majordomo@xxxxxxxxxxxxxxx More majordomo info at http://vger.kernel.org/majordomo-info.html
