Received: with ECARTIS (v1.0.0; list linux-xfs); Wed, 14 Apr 2004 15:55:55 -0700 (PDT) Received: from omx1.americas.sgi.com (cfcafw.sgi.com [198.149.23.1]) by oss.sgi.com (8.12.10/8.12.9) with SMTP id i3EMtpKO024621 for ; Wed, 14 Apr 2004 15:55:51 -0700 Received: from larry.melbourne.sgi.com (larry.melbourne.sgi.com [134.14.52.130]) by omx1.americas.sgi.com (8.12.10/8.12.9/linux-outbound_gateway-1.1) with SMTP id i3EMtg1J025312 for ; Wed, 14 Apr 2004 17:55:44 -0500 Received: from wobbly.melbourne.sgi.com (wobbly.melbourne.sgi.com [134.14.55.135]) by larry.melbourne.sgi.com (950413.SGI.8.6.12/950213.SGI.AUTOCF) via ESMTP id IAA19388; Thu, 15 Apr 2004 08:55:12 +1000 Received: from wobbly.melbourne.sgi.com (localhost [127.0.0.1]) by wobbly.melbourne.sgi.com (SGI-8.12.5/8.12.5) with ESMTP id i3EMt67X232528; Thu, 15 Apr 2004 08:55:08 +1000 (EST) Received: (from nathans@localhost) by wobbly.melbourne.sgi.com (SGI-8.12.5/8.12.5/Submit) id i3EMsxbn232545; Thu, 15 Apr 2004 08:54:59 +1000 (EST) Date: Thu, 15 Apr 2004 08:54:58 +1000 From: Nathan Scott To: brian@krusic.com Cc: linux-xfs@oss.sgi.com Subject: Re: used obsolete MD ioctl... Message-ID: <20040415085458.A232631@wobbly.melbourne.sgi.com> References: <200404141903.AWL88766@ms8.netsolmail.com> Mime-Version: 1.0 Content-type: text/plain; charset=us-ascii Content-Disposition: inline User-Agent: Mutt/1.2.5i In-Reply-To: <200404141903.AWL88766@ms8.netsolmail.com>; from brian@krusic.com on Wed, Apr 14, 2004 at 03:03:35PM -0400 Content-Transfer-Encoding: 8bit X-archive-position: 2811 X-ecartis-version: Ecartis v1.0.0 Sender: linux-xfs-bounce@oss.sgi.com Errors-to: linux-xfs-bounce@oss.sgi.com X-original-sender: nathans@sgi.com Precedence: bulk X-list: linux-xfs Content-Length: 544 Lines: 22 On Wed, Apr 14, 2004 at 03:03:35PM -0400, brian@krusic.com wrote: > Hi, > > First, thanks for the rapid reply. Second, I am using the > latest raidtools v 1.003-2. Instead of using raidtab, I used > mdadm as you suggested and got the same results. > > I can mount the file system and use it however I'm not sure > how production worthy it will be considering the error > message. > > Could this error be bogus? > Its a missing ioctl handler in the MD driver. Its fixed in later 2.4 revisions, and is harmless. cheers. -- Nathan