From: Nick Naym on
.... has been taking forever to perform a backup, and the Console keeps
reporting the following error:


CoreEndianFlipData: error -4940 returned for rsrc type open


What does it mean?

--
iMac (24", 2.8 GHz Intel Core 2 Duo, 2GB RAM, 320 GB HDD) � OS X (10.5.4)

From: David Empson on
Nick Naym <nicknaym@[remove_this].gmail.com> wrote:

> ... has been taking forever to perform a backup, and the Console keeps
> reporting the following error:
>
>
> CoreEndianFlipData: error -4940 returned for rsrc type open
>
>
> What does it mean?

I'm rusty on Mac programming, but I can at least read the fiery letters.

CoreEndianFlipData is a function in Core Services which is responsible
for reversing a series of data bytes. This is used when converting
between "big endian" (high order byte first) and "little endian" (low
order byte first) data formats.

Big endian is the native byte order for PowerPC Macs, little endian is
the native byte order for Intel Macs. Older data structures which
predate Mac OS X are all big endian, so if you have an Intel Mac, there
is a fair amount of this data flipping going on.

Error -4940 is "errCoreEndianDataTooShortForFormat". Judging by the
name, this is a specific error returned by CoreEndianFlipData to
indicate that the caller specified it wanted to do something like flip a
4-byte value, but there weren't enough data bytes supplied.

"rsrc type open" is somewhat vague. "rsrc" is short for "resource",
which is a data structure attached to a file, a standard feature on the
Mac since day one but gradually being phased out under Mac OS X.

Each resource has a four character type. My reading of this message is
that something was trying to read a resource of type 'open'. This is a
resource used to indicate which file types can be opened by an
application.

What it doesn't say is where the problem happened. I think it is
indicating that you have a file somewhere (probably an older
application) which has a damaged 'open' resource. Something is trying to
read this resource regularly and is complaining about it.

The message might not have anything to do with Time Machine.

Have you tried looking at system.log? Time Machine puts more useful
diagnostic information there.

--
David Empson
dempson(a)actrix.gen.nz