bwsw opened a new issue #3447: NFS Cluster-wide storage capacity calculation and overprovisioning URL: https://github.com/apache/cloudstack/issues/3447 <!-- Verify first that your issue/request is not already reported on GitHub. Also test if the latest release and master branch are affected too. Always add information AFTER of these HTML comments, but no need to delete the comments. --> ##### ISSUE TYPE <!-- Pick one below and delete the rest --> * Bug Report ##### COMPONENT NAME <!-- Categorize the issue, e.g. API, VR, VPN, UI, etc. --> ~~~ Core, KVM, NFS ~~~ ##### CLOUDSTACK VERSION <!-- New line separated list of affected versions, commit ID for issues on master branch. --> ~~~ 4.11.2 ~~~ ##### CONFIGURATION <!-- Information about the configuration if relevant, e.g. basic network, advanced networking, etc. N/A otherwise --> Cloudstack with KVM and NFS ##### OS / ENVIRONMENT <!-- Information about the environment if relevant, N/A otherwise --> Ubuntu 16.04 ##### SUMMARY <!-- Explain the problem/feature briefly --> When NFS cluster-wide primary storage is used, the capacity limitations are calculated wrong way: * storage.overprovisioning.factor configured for the storage is not taken into account; ##### STEPS TO REPRODUCE <!-- For bugs, show exactly how to reproduce the problem, using a minimal test-case. Use Screenshots if accurate. For new features, show how the feature would be used. --> Create storage with ` storage.overprovisioning.factor` set to `4`, fill it with thin volumes, detect when it stops to provision new volumes. ##### EXPECTED RESULTS <!-- What did you expect to happen when running the steps above? --> ~~~ Per-storage overprovisioning setting should be taken into consideration ~~~ ##### ACTUAL RESULTS <!-- What actually happened? --> <!-- Paste verbatim command output between quotes below --> ~~~ Per-storage overprovisioning setting is not taken into consideration ~~~
---------------------------------------------------------------- This is an automated message from the Apache Git Service. To respond to the message, please log on to GitHub and use the URL above to go to the specific comment. For queries about this service, please contact Infrastructure at: [email protected] With regards, Apache Git Services
