LUN bigger than volume

[AlexandreOliveira]

Hello, I am seeing this very strange behavior:

# df output

/vol/vol_SQL1_MS1_Data_1/ 3328599656 3180880684  147718972      96%  /vol/vol_SQL1_MS1_Data_1/
/vol/vol_SQL1_MS1_Data_1/.snapshot          0          0          0       0%  /vol/vol_SQL1_MS1_Data_1/.snapshot

#lun output

LUN name: /vol/vol_SQL1_MS1_Data_1/SQL1_MS1_SQLData_1.lun

Lun size : 5046636994560

How can I have a 4.7TB LUN inside a 3.1TB volume?

Some points to consider:
- Volume has space guarantee set to volume.
- LUN has space reservation disable
- LUNs expansions are managed via SnapDrive on Windows

Thanks!

[aborzenkov]

---

@AlexandreOliveira wrote:

How can I have a 4.7TB LUN inside a 3.1TB volume?

You answered it yourself:

---

@AlexandreOliveira wrote:

- LUN has space reservation disable

[AlexandreOliveira]

But shouldn´t the LUN size be limited to the volume size?

[keitha · Accepted solution]

No. You can certainly have a LUN much larger than the volume. Think of the LUN as the presentation to the outside work. How much space do you want the host to see. The volume then is how much space do you think the data is actually going to take. This way unused space in the LUN and duplicate and compressible data is not consuming space in the volume. You can of course change the volume size up or down on the fly without the host being aware.

[Mjizzini]

You set up is valid. Note that the LUN will go offline when the volume will be full.

You can have a bigger volume with no space guaranty (thin prevision) or Make sure you have volume autosize set.

volume autosize

[AlexandreOliveira]

Just a correction, the LUN will not go offline when the volume gets full. It will probably go offline when the aggregate goes full.