Skip to content

fix for failed reads when client.local_extents=1 #680

New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Merged
merged 1 commit into from
Sep 3, 2021

Conversation

MichaelBrim
Copy link
Collaborator

Description

Fixes a couple bugs in the client-local read path that prevented local read operations from completing successfully.

Motivation and Context

Unit tests and example runs were failing when setting UNIFYFS_CLIENT_LOCAL_EXTENTS=1

How Has This Been Tested?

Tested on OLCF Summit and in Ubuntu Docker

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.

@MichaelBrim
Copy link
Collaborator Author

@adammoody please look over and merge asap

@adammoody adammoody merged commit ea783de into LLNL:dev Sep 3, 2021
@adammoody
Copy link
Collaborator

Thanks @MichaelBrim and @CamStan

@MichaelBrim MichaelBrim deleted the local-extents-read-fix branch September 3, 2021 20:47
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

Successfully merging this pull request may close these issues.

3 participants