fix for truncate broadcast ENOENT

[MichaelBrim]

Description

Adam's recent PR #587 adds a call to unifyfs_fid_truncate() when a file is created with O_TRUNC. This is correct behavior, but the change introduced new server error messages when running our examples that use testutil for N-1 shared files. The errors show up when processing the truncate broadcast rpc at non-owner servers where the inode has not yet been created, since only client rank 0 does the create.

The fix is to not treat the missing inode as an error on non-owner servers.

Types of changes

• Bug fix (non-breaking change which fixes an issue)
• New feature (non-breaking change which adds functionality)
• Performance enhancement (non-breaking change which improves efficiency)
• Code cleanup (non-breaking change which makes code smaller or more readable)
• Breaking change (fix or feature that would cause existing functionality to change)
• Testing (addition of new tests or update to current tests)
• Documentation (a change to man pages or other documentation)

Checklist:

• My code follows the UnifyFS code style requirements.
• I have updated the documentation accordingly.
• I have read the CONTRIBUTING document.
• I have added tests to cover my changes.
• All new and existing tests passed.
• All commit messages are properly formatted.

[adammoody]

Good idea, @MichaelBrim .

[adammoody]

@CamStan , I optimistically merged this, but it'd be good to run your test once more to verify that truncate ENOENT message is gone.

[CamStan]

Verified. The truncate ENOENT message I was seeing is gone with this fix.