Fix for ressource fork handling on Solaris

Fix for ressource fork handling on Solaris

For certain metadata operations the ressourcefork size was
reported as 0 bytes although an existing ressource fork was
> 0 bytes. As a result when copying files with ressource forks
from the server to the client the ressource was ignored by the
client and not copied.