Different volume size in "df -Vh" and "vol size" output

[DHAKSHINAMOORTHY_B]

Hi All,

df -Vh and vol size output showing different sizes in one of our DB Server volume which is in snapmirror. Please find the below output, let me know why this difference came.

Filer2> df -Vh DBVOLUME

Filesystem               total       used      avail capacity  Mounted on

/vol/DBVOLUME/     2805GB     2162GB      642GB      77%  /vol/DBVOLUME/

/vol/DBVOLUME/.snapshot        0MB      320MB        0MB     ---%  /vol/DBVOLUME/.snapshot

Filer2>

Filer2> vol size DBVOLUME

Warning: Volume 'DBVOLUME' has fs_size_fixed option set.  The file system

size may differ from the volume size.

See 'vol status -b' for more detail.

vol size: Flexible volume 'DBVOLUME' has size 4806g.

Filer2>

Filer2> vol options DBVOLUME

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

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

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

fs_size_fixed=on, 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, dlog_hole_reserve=off

Filer2>

[JGPSHNTAP]

it's a snapmirror target, do vol size on source

[martin_fisher]

The volume is a snapmirror destination, so as JGPSHNTAP has suggested, run the commands on your source volume.

the 'vol size' command will return the size of the volume, where as the 'df' (disk free) will return info regarding space utilization.

A volume can be hugely oversized, when compared to the totals reported using df.