Received: by oss.sgi.com id ; Wed, 14 Feb 2001 22:01:42 -0800 Received: from pipt.oz.cc.utah.edu ([155.99.2.7]:32968 "EHLO pipt.oz.cc.utah.edu") by oss.sgi.com with ESMTP id ; Wed, 14 Feb 2001 22:01:23 -0800 Received: from localhost (jdr1529@localhost) by pipt.oz.cc.utah.edu (8.9.2/8.9.2) with ESMTP id XAA16912 for ; Wed, 14 Feb 2001 23:01:08 -0700 (MST) Date: Wed, 14 Feb 2001 23:01:08 -0700 (MST) From: james rich To: linux-xfs@oss.sgi.com Subject: build failure update and raid 0 Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-linux-xfs@oss.sgi.com Precedence: bulk Return-Path: X-Orcpt: rfc822;linux-xfs-outgoing I have an update on the build problems I'm having in cmd/*. If I enter (for example) cmd/xfsprogs and type make the build fails. But if I enter each subdirectory of xfsprogs and type make everything builds fine. So the problem seems to be with the top level Makefile building invalid targets. I'll investigate and hopefully come up with the right answer. I also thought I should mention that I am running xfs on a raid level 0 device (using the md driver). The XFS FAQ mentions that xfs hasn't been tested with raid and that people using it should let folks know how it works. The FAQ also says that xfs will not work with the md driver and the kiobuf option enabled. Now I don't remember if the kiobuf option is enabled, but xfs is working beautifully on md0. Any tests anyone would like me to try? The data on md0 doesn't matter so no problem if I lose it all (it would suck to lose stuff on the other devices though). James Rich james.rich@m.cc.utah.edu