vol to lun 1:1?

TDUBB1234 — Thu, 05 Jun 2025 06:23:04 GMT

is it best practice to create vol and lun on a 1:1 ratio?

---------------------------------------------------------------------------------------------------------------------------------------

Aggregate 'x'

Total space WAFL reserve Snap reserve Usable space BSR NVLOG A-SIS Smtape

3310GB 331GB 148GB 2830GB 0KB 0KB 0KB

Space allocated to volumes in the aggregate

Volume Allocated Used Guarantee

vol1 127GB 124GB none

Aggregate Allocated Used Avail

Total space 127GB 124GB 2703GB

Snap reserve 148GB 1980MB 147GB

WAFL reserve 331GB 2262MB 328GB

-----------------------------------------------------------------------------------------------------------------------------------

df -V -h

Filesystem total used avail capacity Mounted on

/vol/vol0/ 500GB 130GB 369GB 26% /vol/vol0/

/vol/vol0/.snapshot 0MB 317MB 0MB ---% /vol/vol0/.snapshot

---------------------------------------------------------------------------------------------------------------------------------

lun show

/vol/vol0/vol0_qtr/lun0 500.1g (536952700928) (r/w, online, mapped)

/vol/vol0/vol0_qtr/lun1 500.1g (536952700928) (r/w, online, mapped)

--------------------------------------------------------------------------------------------------------------------------

/vol/vol0/vol0_qtr/lun0 500.1g (536952700928) (r/w, online, mapped)

Serial#: dfkoFJkkO42q

Share: none

Space Reservation: disabled

Multiprotocol Type: vmware

Maps: igroup=4

Occupied Size: 103.5g (111101456384)

Creation Time: Thu Jun 21 19:19:45 PDT 2012

Cluster Shared Volume Information: 0x0

/vol/vol0/vol0_qtr/lun1 500.1g (536952700928) (r/w, online, mapped)

Serial#: dfkoFJl9MQbp

Share: none

Space Reservation: disabled

Multiprotocol Type: vmware

Maps: igroup=5

Occupied Size: 26.7g (28669276160)

Creation Time: Wed Jul 11 16:03:40 PDT 2012

Cluster Shared Volume Information: 0x0

-------------------------------------------------------------------------------------------------------------

vol options vol0

nosnap=off, nosnapdir=off, minra=off, no_atime_update=off, nvfail=off,

ignore_inconsistent=off, snapmirrored=off, create_ucode=off,

convert_ucode=off, maxdirsize=45875, schedsnapname=ordinal,

fs_size_fixed=off, compression=off, guarantee=none, svo_enable=off,

svo_checksum=off, svo_allow_rman=off, svo_reject_errors=off,

no_i2p=off, fractional_reserve=0, extent=off, try_first=volume_grow,

read_realloc=off, snapshot_clone_dependency=off, nbu_archival_snap=off

-----------------------------------------------------------------------------------------------------------------

since my vol0 is only at 500gb, why am I amble to create 2 luns of 500gb each on this vol? Is this because of thin provision?

Re: vol to lun 1:1?

arunchak — Thu, 12 Jul 2012 02:42:55 GMT

HI,

If you are having only LUN inside a volume, then 1 LUN per volume should be fine.

If you want to have multiple LUNs in a volume then its a better approach to create multiple qtrees in the volume and have one LUN per qtree.

Space reservation has been disabled on your LUN, maybe thats the reason you are able to create 2 LUNs of 500 GB. (Also they are thin provisioned).

Thanks,

Arun

topic Re: vol to lun 1:1? in VMware Solutions Discussions

vol to lun 1:1?

Re: vol to lun 1:1?