Subscribe

Vol almost full dfm event

 

A Warning event at 24 Jan 10:39 AUS Eastern Daylight Time on Volume tbpnapv002_vol1 on vFiler tbpnapv002:

The volume is 70.19% full (using 1.12 TB of 1.60 TB). There is 0 bytes of spare disk space available for expanding the volume.

I saw this event from dfm and I am bit concerned about 

There is 0 bytes of spare disk space available for expanding the volume.

This is my existing config on the storage controllers for the above volume tbpnapv002_vol1

vol options tbpnapv002_vol1

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

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

convert_ucode=off, maxdirsize=73400, 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

vol autosize tbpnapv002_vol1

Volume autosize is currently ON for volume 'tbpnapv002_vol1'.

The volume is set to grow to a maximum of 4 TB, in increments of 500 GB.

Why does the dfm reporting as There is 0 bytes of spare disk space available for expanding the volume.

Any help ThanksSmiley Happy

Re: Vol almost full dfm event

In the volume and aggr full alert we embed the message of how much aggr free space and how many spare disk are available respectively in each case.

Is this volume a traditional volume ? I ask because we get the message of spare disk only in case of trad vol. As in order to grow a trad vol you need spare disk.

Can you get the output of the following ?

dfm event detail for the event id ?

dfm version

Ontap version of the volume.

Regards

adai

Re: Vol almost full dfm event

Hi,

This is a bug. Kindly add your call_rec into the bug 566576.

-KJag

Re: Vol almost full dfm event

Hi,

     The issue was reproducible and also root cause found.

The suggestion statement is coming from the times of Traditional volumes when spare disks were required to expand the volumes.But with the flexible volume we should rather look at the aggr free space.

The second problem is for a vfiler volume we try to get number of spare disk, but disk are child of filer and not vfiler. Thats why you get 0 spare disk. If the volume is from a filer rather than vfiler you will get the suggestion with the sum of the sizes of the spare disks.

Regards

adai

Re: Vol almost full dfm event

I have same "problem"

There is 0 bytes of spare disk space available for expanding the volume.

vol status vn1010_ebsdata3

         Volume State           Status            Options

vn1010_ebsdata3 online          raid_dp, flex     create_ucode=on,

                                mirrored          convert_ucode=on,

                                                  maxdirsize=80000

                Containing aggregate: 'aggr3'

vol options vn1010_ebsdata3

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

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

convert_ucode=on, maxdirsize=80000, 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=100, extent=off, try_first=volume_grow,

read_realloc=off, snapshot_clone_dependency=off

vol autosize vn1010_ebsdata3

Volume autosize is currently OFF for volume 'vn1010_ebsdata3'.