weizhouapache commented on PR #8481:
URL: https://github.com/apache/cloudstack/pull/8481#issuecomment-1884729728

   > code looks good. I have a worry though. overprovisioning on storage in 
general is a dangerous thing. On cpu and memory any errors due to 
overprovisioning are likely to not be fatal, but on storage these can easily 
lead to data loss. when storage is allocated but not used we can apply 
overprovisioning but when parts of it get used these should not be considered 
in overprovisioning. I don't think our model supports such behaviour. any ideas 
@GutoVeronezi @sureshanaparti  (sorry, i don't know what wisdom is in respect 
to this)
   
   @DaanHoogland 
   I believe most cloudstack users use thin provisioning and storage 
overprovisioning. It was never a critical issue, there was no data loss either. 
If the storage is almost occupied, users should consider adding more storage 
before reaching full disk space.
   


-- 
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.

To unsubscribe, e-mail: [email protected]

For queries about this service, please contact Infrastructure at:
[email protected]

Reply via email to