[Top] [All Lists]

Re: fseek returning incorrect values

To: Steve Lord <lord@xxxxxxx>
Subject: Re: fseek returning incorrect values
From: "Sean Kormilo" <skormilo@xxxxxxxxxxxxxxxxxx>
Date: 20 Jun 2002 14:44:50 -0400
Cc: linux-xfs@xxxxxxxxxxx
In-reply-to: <1024593881.5039.64.camel@xxxxxxxxxxxxxxxxxxxx>
References: <1024586614.23218.46.camel@xxxxxxxxxxxxxxxxxxxxxx> <1024593881.5039.64.camel@xxxxxxxxxxxxxxxxxxxx>
Sender: owner-linux-xfs@xxxxxxxxxxx

I don't hate you. How could I hate the principal engineer for Linux XFS?

It isn't feasible for me to change kernels at this point. The downside
to being on PowerPC hardware is that I have some 3rd party (read
non-open source) dependencies that prevent me upgrading from 2.4.5 until
sometime in the fall.

I've asked the application owner to make a change to not seek past the
end of the file, but to write dummy data instead to achieve the same
effect. My only concern is that there may be other applications which
attempt to do the same thing and are inadvertently causing file

If you should happen to think of (or happen to run across) the lseek
path change, and think it could be patched back into the 1.0.1 XFS
release, please let me know.



> On Thu, 2002-06-20 at 10:23, Sean Kormilo wrote:
> > Hi,
> > 
> > I'm running XFS under PowerPC linux. Kernel version 2.4.5 with XFS 1.0.1
> > release code patched in.
> You are going to hate me for this, but there is no way we can support 
> problems in a kernel this old. Can you possibly try a recent kernel,
> we definitely changed the lseek path, but I cannot remember when.
> Steve
> -- 
> Steve Lord                                      voice: +1-651-683-3511
> Principal Engineer, Filesystem Software         email: lord@xxxxxxx

Sean C. Kormilo, SAM21/STORM Software Architect, Nortel Networks
              email: skormilo@xxxxxxxxxxxxxxxxxx

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