12:18 a.m.
Hi Ladislav,
Not sure if you sam my reply, so i give it another shot.
I just want to he clear on understanding what you wrote in your recommendation.
Please check my previous reply.
Thank you.
Sent from my iPhone
On 6 Nov 2019, at 11:52, Vrgotic, Marko <M.Vrgotic(a)activevideo.com> wrote:
Hi Ladislav,
Thank you for the reply.
On the matter of your Recommendation, when you mention free space, were you referring
to:
* Space that is free/unallocated on the Aggregate, allowing the AutoGrow
* Or all that is allocated to the volume but not actual Data Space
Kindly awaiting your reply.
-----
kind regards/met vrindelijke groet
Marko Vrgotic
ActiveVideo
From: Ladislav Humenik <ladislav.humenik(a)ionos.com>
Date: Tuesday, 5 November 2019 at 20:45
To: "Vrgotic, Marko" <M.Vrgotic(a)activevideo.com>
Cc: "users(a)ovirt.org" <users(a)ovirt.org>
Subject: Re: [ovirt-users] Re: oVirt and Netapp question
Hi,
for the NetApp part, here is copy-paste from the netapp kb:
Answer
The volume "Over Provisioned Space" value provided in OnCommand System Manager
(OCSM) is the "Over Provisioned Size" field provided by the volume
show<https://docs.netapp.com/ontap-9/topic/com.netapp.doc.dot-cm-cmpr-...
at the cluster shell.
This value is determined by the following formula:
(volume size) - (volume used) - (volume space available) - (snapshot used space) ==
storage that can't be provided by the aggregate if written to the volume
for the ovirt part:
Ovirt will see the volume size available within thin-volume without any knowledge of the
aggregate space (available/or not) in behind.
Recommendation:
on netapp side do volume auto-grow and you are safe as long as you have free space inside
aggregate.
HTH
On 05.11.19 14:54, Vrgotic, Marko wrote:
Second attempt 😊
From: "Vrgotic, Marko"
<M.Vrgotic@activevideo.com><mailto:M.Vrgotic@activevideo.com>
Date: Monday, 4 November 2019 at 14:01
To: "users@ovirt.org"<mailto:users@ovirt.org>
<users@ovirt.org><mailto:users@ovirt.org>
Subject: oVirt and Netapp question
Dear oVirt,
Few months ago our production environment oVirt with main Shared storage via NFS Netapp is
live.
We have been deploying VMs with thin provisioned HDD 40GB based template, CentOS 7.
The Netapp NFS v4 storage volume is 7TB in size, also Thin Provisioned.
First attached screenshot shows the space allocation of the production volume from Netapp
side.
Is there anyone in oVirt community who would be able to tell me the meaning of the 5.31 TB
Over Provisioned Space?
<image001.png>
Second attached is the info of the production volume from oVirt side:
<image002.png>
What I want to understand is the way how is oVirt reading the volume usage and Netapp and
where is the difference.
Is the Over Allocated Space something that is just logically used/reserved and will be
intelligently re-allocated/re-used as the actual Data Space Used grows or am I looking at
oVIrt actually hitting Critical Space Action Blocker and will have to resize the volume?
If there is anyone from Netapp or with good Netapp experience that is able to help
understanding the data above better, thank you in advance?
Kindly awaiting your reply.
-----
kind regards/met vrindelijke groet
Marko Vrgotic
ActiveVideo
_______________________________________________
Users mailing list -- users@ovirt.org<mailto:users@ovirt.org>
To unsubscribe send an email to
users-leave@ovirt.org<mailto:users-leave@ovirt.org>
Privacy Statement: https://www.ovirt.org/site/privacy-policy/
oVirt Code of Conduct: https://www.ovirt.org/community/about/community-guidelines/
List Archives:
https://lists.ovirt.org/archives/list/users@ovirt.org/message/BVGZMJHNNM3...
