xfs
[Top] [All Lists]

Re: Locking problems

To: Steve Lord <lord@xxxxxxx>
Subject: Re: Locking problems
From: Andi Kleen <ak@xxxxxxx>
Date: Mon, 26 Aug 2002 20:06:58 +0200
Cc: Chris Tooley <ctooley@xxxxxxxx>, linux-xfs@xxxxxxxxxxx
In-reply-to: <1030381936.28544.22.camel@xxxxxxxxxxxxxxxxxxxx>
References: <1030377163.28487.16.camel@xxxxxxxxxxxxxxx> <1030381936.28544.22.camel@xxxxxxxxxxxxxxxxxxxx>
Sender: linux-xfs-bounce@xxxxxxxxxxx
User-agent: Mutt/1.3.22.1i
On Mon, Aug 26, 2002 at 12:12:16PM -0500, Steve Lord wrote:
> 
> On Mon, 2002-08-26 at 10:52, Chris Tooley wrote:
> > 
> > We're running a point of sale system on Linux and have put the data on
> > an XFS partition.  Unfortunately there has been consistent corruption of
> > the data during writes to the database.  Since the database is an ISAM
> > database, it's all stored in files that are opened and closed a lot. 
> > The vendor of the point of sale is blaming XFS for the corruption.  The
> > application is an old COBOL app that is using the binary compatability
> > modules to run.  Are there any known problems with corruption when using
> > these binary compatability libraries with 1.1?
> 
> I am not aware of any specific corruption issues in 1.1, I know
> nothing of the 'binary compatibility modules you are referring
> to. Is this for running things like a.out binaries?

Suspect he refers to the iBCS/Linux ABI patches for SCO etc. emulation.
Christoph should know more about it, he used to maintain that stuff.

I doubt it can cause specific data corruption thought - read/write
should be directly handed through to the linux implementations because
there is not much to emulate there.

> 
> Do you have any information about the pattern of the corruption, or
> the types of I/O being done to the files?

Point-Of-Sale sounds like it'll be often power cycled without proper
shutdown. This could cause problems if the HD does write buffer a lot of data
on its own. I would try applying the ordered writing patches or at least
turn off the write cache of the HD.

-Andi


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