[PVFS2-developers] Determining meaning of error code on I/O

[neillm at mcs.anl.gov]

On Mon, Jul 12, 2004 at 07:08:50PM -0400, Dean Hildebrand wrote:
> Can anyone tell me what error -1073741828 means (-0x40000004)?  The first
> time I write to a new file it works fine, but the second time I get this
> error.  I can't seem to find this error in a table anywhere.  It is always
> the same error though, so I don't think it is just garbage.

RobL answered that correctly, though I'll take the opportunity to say
that we now have a PVFS_strerror_r function that's analogous to
strerror_r (the thread safe strerror function) that looks like:

int PVFS_strerror_r(int errnum, char *buf, int n);

It handles PVFS2 error codes and 'normal' (errno) error codes as well.

This error code translation question has been asked several times on
IRC, so I'm advertising another way to do it ;-)

> ps: The trace may look a little wierd since I'm not getting the file
> attributes directly from the PVFS2 server, but instead injecting them from
> the NFSv4 client.

<snip>

> getattr_acache state: lookup
> getattr_acache state: fs_id:925967295 handle:2147483649
> PINT_acache_lookup entered
> PINT_acache_lookup exiting
> getattr_acache state: Found!

You've modified the getattr_acache state machine to grab attrs from
the NFSv4 client?  I'm curious how your pNFS work is going, so if you
want to describe what you're doing a bit more or join us on IRC, I'm
all ears :-)

Also, does it matter that most of the code path you've pasted in has
been heavily modified somewhat recently?  Are you planning to keep
your changes up to date alongside the pvfs2 source tree?

-Neill.