The problems we are seeing are with an old application that uses the SCO
OpenUnix and Unixware binary compatability modules. They can be found
at abi.sourceforge.net and are for running applications built for other
systems on Linux. RedHat includes them but I've also tried patching
different ways.
I'm currently running 2.4.19 vanilla plus the abi patches plus the XFS
patch. I've tried a lot of different kernel rpms and all have come up
with the same issues. I've got some machines using nfs to get at the
data and some machines using ssh. It doesn't seem to make a difference
which they are using, or if we even just provide ssh access.
Chris Tooley
On Mon, 2002-08-26 at 12:12, 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?
>
> Do you have any information about the pattern of the corruption, or
> the types of I/O being done to the files?
>
> Steve
>
> >
> > Chris Tooley
> >
> >
> --
>
> Steve Lord voice: +1-651-683-3511
> Principal Engineer, Filesystem Software email: lord@xxxxxxx
|