abnormal automatic increase size on snapmirror source volume

[aroussea]

Hello,

A volume which have a LUN had an four abnormal automatic increase since two days (350Go origin volume capacity). Never this volume and the LUNs a more used capacity. You can view some results below:

vol options vol_name

nosnap=off, nosnapdir=off, minra=off, no_atime_update=off, nvfail=off,
ignore_inconsistent=off, snapmirrored=off, create_ucode=on,
convert_ucode=on, maxdirsize=335462, schedsnapname=ordinal,
fs_size_fixed=off, compression=off, guarantee=volume, 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

df -g vol_name
Filesystem               total       used      avail capacity  Mounted on
/vol/vol_name/      430GB      217GB      212GB      51%  /vol/vol_name/
/vol/vol_name/.snapshot        0GB        6GB        0GB     ---%  /vol/vol_name/.snapshot

vol autosize vol_name

Volume autosize is currently ON for volume 'vol_name'.
The volume is set to grow to a maximum of 14712 GB, in increments of 19 GB.

Alexandre

[aroussea]

Other information:

snap autodelete vol_name
snapshot autodelete settings for vol_vmmlib_01:
state                           : off
commitment                      : try
trigger                         : volume
target_free_space               : 20%
delete_order                    : oldest_first
defer_delete                    : user_created
prefix                          : (not specified)
destroy_list                    : none

snap reserve vol_name

Volume vol_name: current snapshot reserve is 0% or 0 k-bytes.

lun show -v /vol/vol_name/server_name_11.lun
        /vol/vol_name/server_name_11.lun  210.0g (225537177600)  (r/w, online, mapped)

[enrjfitz1]

Hi, looking at this the volume is obviously not full. If the LUN is 210Gb and the volume is 400+Gb then there is plenty of space.

What I would be looking for is the trigger for the Autogrow. With Autogrow you can specify at what point the volume grows, for example if it gets 70% full or 50% full then initiate an autogrow.

Also, can you see the event logs and see the point at which the volume grew? It should give you a reason for the autogrow.

Can you find this information out?

[aroussea]

vol autosize vol_name

Volume autosize is currently ON for volume 'vol_name'.
The volume is set to grow to a maximum of 14712 GB, in increments of 19 GB.

Nothing in Windows Events Logs and this message on filer /etc/messages

Wed Nov 3 21:13:53 CET [filer: wafl.vol.autoSize.done:info]: Automatic increase size of volume 'vol_name' by 19922944 kbytes done.

[aroussea]

Print flag

wafl_reclaim_threshold_t = 0x55
wafl_reclaim_threshold_s = 0x5a
wafl_reclaim_threshold_m = 0x5c
wafl_reclaim_threshold_l = 0x5f
wafl_reclaim_threshold_xl = 0x62