-
Notifications
You must be signed in to change notification settings - Fork 218
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
Enable support for LUN's "space-allocation" flag #135
Comments
hi @adkerr - I didn't find any |
Thanks for the PR. Next we'll import the commit into our internal CI system and also code review the changes. If we agree with the changes and everything looks good test-wise we'll push it back out automatically. If we need any other updates from you we'll make sure the update the PR on github |
Hi @stang - we've been heads down on some big rock features (Vol Import, CRDs, and other stuff)... sorry this has dragged on. Before we can review your code, we'd need you to sign our Corporate CLA. Is that something you'd be willing to consider? That's the first step. Still not sure what release we are targeting on this one, but can't do anything without the CCLA. I'll send it to you via thePub (Slack). Thanks! |
Added in version 19.07 |
trident version:
18.01.0
backend:
ontap-san
guest os:
ubuntu16.04
We currently can't enable the
space-allocation
property when a LUN is created.That option is required in order to allow the host OS to claim back some space (via
fstrim
for example) when usingthin provisioning
.That have multiple consequences:
readonly
in the guest os.That really limit the usages and can have unexpected impact on a deployment.
The text was updated successfully, but these errors were encountered: