Skip to content
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

Reduce size of zvol and enforce 4k blocksize in zvol tests #5845

Merged
merged 1 commit into from
Mar 1, 2017

Conversation

dinatale2
Copy link
Contributor

Description

Poor write performance on 32-bit buildbot builders is causing zvol ENOSPC testing to time out.

Motivation and Context

Adjust zvol size to be 256mb instead of 1g to ensure the ENOSPC testing finishes within the 10min timeout. Ensure block size is 4k which should match page sizes.

How Has This Been Tested?

Ubuntu 14.04 EC2 instance running the same AMI the 32-bit builders run.

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)

Checklist:

  • My code follows the ZFS on Linux 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.
  • Change has been approved by a ZFS on Linux member.

@mention-bot
Copy link

@dinatale2, thanks for your PR! By analyzing the history of the files in this pull request, we identified @behlendorf, @sydneyvanda and @ahrens to be potential reviewers.

@dinatale2
Copy link
Contributor Author

Corrected an issue with how I was setting create_args in the lib. If you wouldn't mind taking another glance at it @kpande

@@ -39,8 +39,9 @@ DISK=${DISKS%% *}
if is_mpath_device $DISK; then
delete_partitions
fi
BLOCKSIZE="4K"
Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

We should define this in zvol.cfg with the others

@dinatale2
Copy link
Contributor Author

Do you want me to introduce blocksize to each default_zvol_setup call as well?

Copy link
Contributor

@behlendorf behlendorf left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

No, let's keep this fix currently confined to the problematic test case

@@ -35,18 +35,25 @@
# Create a simple zvol volume
#
# Where disk_device: is the name of the disk to be used
# volume_size: is the size of the volume, e.g. 2G
# volume_size: is the size of the volume, e.g. 2Gi
Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Stray trailing i

@dinatale2 dinatale2 force-pushed the zvol_ENOSPC_fix branch 2 times, most recently from 9891acc to fc00977 Compare February 28, 2017 18:30
32 bit builders in the buildbot are having trouble completing
their ENOSPC testing. Reduce the zvol size and ensure we use
4k blocksizes so the test is less likely to time out.

Signed-off-by: Giuseppe Di Natale <[email protected]>
@behlendorf behlendorf merged commit ebd9aa8 into openzfs:master Mar 1, 2017
@dinatale2 dinatale2 deleted the zvol_ENOSPC_fix branch March 1, 2017 21:12
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

4 participants