xfs
[Top] [All Lists]

Re: Locking problems

To: Chris Tooley <ctooley@xxxxxxxx>
Subject: Re: Locking problems
From: Christoph Hellwig <hch@xxxxxxxxxxxxx>
Date: Mon, 26 Aug 2002 19:45:27 +0100
Cc: Andi Kleen <ak@xxxxxxx>, Steve Lord <lord@xxxxxxx>, linux-xfs@xxxxxxxxxxx
In-reply-to: <1030385436.31858.20.camel@xxxxxxxxxxxxxxx>; from ctooley@xxxxxxxx on Mon, Aug 26, 2002 at 01:10:36PM -0500
References: <1030377163.28487.16.camel@xxxxxxxxxxxxxxx> <1030381936.28544.22.camel@xxxxxxxxxxxxxxxxxxxx> <20020826200658.A32118@xxxxxxxxxxxxx> <1030385436.31858.20.camel@xxxxxxxxxxxxxxx>
Sender: linux-xfs-bounce@xxxxxxxxxxx
User-agent: Mutt/1.2.5.1i
On Mon, Aug 26, 2002 at 01:10:36PM -0500, Chris Tooley wrote:
> > 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'm still looking after it.

> > 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.

*nod* - all emulations use write directly, and the only change in read for
certain personalities is to allow read ond directories, returning sysvfs
dirent.

> > 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.
> >
> The application is a linux application and runs in text mode only. 
> There is no gui.  I can cause the same problems when I only allow ssh
> access to it as well.  That means no reseting because I don't restart
> the server.

Why do you need linux-abi then if it's a native application?


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