I have been reading this how-to about thin and thick volume, but I am still confused about it ( https://www.qnap.com/en/how-to/knowledg ... ick-volume ).
So to my understanding, is that when i setup a thin volume it should grow in size as long as there is space in the storage pool?Thin Volumes allocate space in the storage pool as data is written into the volume. Only the size of data in the volume is used up from the pool space, and free space in the volume does not take up any pool space. If data is deleted from the volume, that space can be freed and given back to the storage pool free space.
This is my setup:
QNAP TS-453D (Firmware 4.5.4.1723)
4x6TB Seagate Ironwolf (One single Raid group and RAID5)
This what i have done:
1) Storage Pool (utilize all the space available)
2) I have setup multiple volumes (Dashboard-Storage&Snapshots->Storage->Storage/Snapshot->Create->New Volume 3) I then select "Thin volume" and click Next, from there i give it a name, set a size and follow default suggestion of 32K.
So my question actually boils down to my understanding of the how-to guide AND the quoted text in the beginning.
1) How i understand this is that a thin volume should expand when more data is written to it
2) The size I set is just a initial size and not maximum
3) Have i completely misunderstood how thin volume works?
I simply want that each of the thin volumes to pull the needed resources (space) they need from the Storage pool in the system, when they need it.
4) Could it be that the seize i set during configuration of thin volume is the maximum size its allowed to take from the pool? So if i really wanted flexibility i should set this size much-much higher. And then carefully monitor the actual usage of the data used from the storage pool. To my understanding is that if I over-provisioning the volumes compared to storage pool much can go wrong.