[Top] [All Lists]

Re: Locking problems

To: linux-xfs@xxxxxxxxxxx
Subject: Re: Locking problems
From: Chris Tooley <ctooley@xxxxxxxx>
Date: 28 Aug 2002 17:41:22 -0500
In-reply-to: <1030456601.16698.6.camel@xxxxxxxxxxxxxxxxxxxx>
References: <1030377163.28487.16.camel@xxxxxxxxxxxxxxx> <20020826190700.GB1894@xxxxxxxxxxxxxxxxxxxxxxxxxxx> <1030396680.32227.1.camel@xxxxxxxxxxxxxxx> <3D6B2C00.33549A97@xxxxxxxxxxxxxxxx> <1030456397.454.2.camel@xxxxxxxxxxxxxxx> <1030456601.16698.6.camel@xxxxxxxxxxxxxxxxxxxx>
Sender: linux-xfs-bounce@xxxxxxxxxxx
OK, it's running fine on ext2.  What are the next steps to see if we can
rid ourselves of the problem with XFS?  I'd like to help with this, but
don't know what we need to do to help.


On Tue, 2002-08-27 at 08:56, Steve Lord wrote:
> On Tue, 2002-08-27 at 08:53, Chris Tooley wrote:
> > 
> > It's not a power cycle problem.  I never power cycle the server and as
> > it happens when the only method of launching the app is via a secure
> > shell to the server, the processes are there.  We don't have a problem
> > with having to power cycle the computers.
> > 
> > I doubt it is write caching, but where would I look to turn that off?
> > 
> > At this point I've had to move the data, format as ext2 and move the
> > data back.  It's not been tested yet, though I expect the same results
> > via ext2.
> Well if you do get the same result then it has got to be the
> application. 
> The cache questions were all based around assumptions about power being
> lost, if the server never goes down, and the application is running on
> the server, then you do not have to worry in that area.
> Steve
> -- 
> Steve Lord                                      voice: +1-651-683-3511
> Principal Engineer, Filesystem Software         email: lord@xxxxxxx

<Prev in Thread] Current Thread [Next in Thread>