Received: (from majordomo@localhost) by oss.sgi.com (8.11.2/8.11.3) id g0B5Hp909136 for linux-xfs-outgoing; Thu, 10 Jan 2002 21:17:51 -0800 Received: from coredump.sh0n.net (qmailremote@CPEdeadbeef0000.cpe.net.cable.rogers.com [24.100.234.67]) by oss.sgi.com (8.11.2/8.11.3) with SMTP id g0B5Hhg09114 for ; Thu, 10 Jan 2002 21:17:44 -0800 Received: (qmail 29368 invoked from network); 11 Jan 2002 04:18:31 -0000 Received: from coredump.sh0n.net (sh0n@24.100.234.67) by coredump.sh0n.net with SMTP; 11 Jan 2002 04:18:31 -0000 Date: Thu, 10 Jan 2002 23:18:30 -0500 (EST) From: Shawn Starr To: Steve Lord cc: Keith Owens , Subject: Re: ANNOUCEMENT: XFS support to the -mjc 2.4.17 branch (fwd) In-Reply-To: <1010674112.17381.1.camel@jen.americas.sgi.com> Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-linux-xfs@oss.sgi.com Precedence: bulk Status: O Content-Length: 1012 Lines: 33 Another person and I have decided to stop -mjc porting for now. because we dont know what will break XFS. so we're forming out own branch and using some patches from -mjc but at a slower pace (first patch is riel's rmap-11a which im suspicous of) but once we can isolate it down. The next step is to fix :) Shawn. On 10 Jan 2002, Steve Lord wrote: > On Wed, 2002-01-09 at 20:57, Shawn Starr wrote: > > > > I'm on a moving target so if things break they break. But i'm not sure. > > User's using my patch have not had file corruption or such. But aside from > > that fxc program which seems to cause problems with XFS (unknown reasons). > > We're doing ok. > > It does not cause any problems in our tree - it has been running for > about 18 hours here without a snag now. Are you saying that the tree > it was dying in was the mjc branch? > > Steve > > > -- > > Steve Lord voice: +1-651-683-3511 > Principal Engineer, Filesystem Software email: lord@sgi.com > >