.Snapshot & snapreserve

[dirkslechten]

Hello,

by default each volume that you create has a .snapshot directory when you do a df -V -h

but with one volume I have a snap reserve.

see attachment

what is the difference between the two and what did i do wrong?

[prakash_aviva]

This is due to one of the volume options "nosnapdir".

Check my outputs of "df" and "vol options" commands for 2 volumes:

Filer> df -Vh GBRLON05VF001_TST03
Filesystem               total       used      avail capacity  Mounted on
/vol/GBRLON05VF001_TST03/     1024GB      156KB     1023GB       0%  /vol/GBRLON05VF001_TST03/
/vol/GBRLON05VF001_TST03/.snapshot      256GB        0KB      256GB       0%  /vol/GBRLON05VF001_TST03/.snapshot

Filer> df -Vh OS_DUMP
Filesystem               total       used      avail capacity  Mounted on
/vol/OS_DUMP/            100GB      144KB       99GB       0%  /vol/OS_DUMP/
snap reserve               0KB        0KB        0KB     ---%  /vol/OS_DUMP/..

Filer> vol options GBRLON05VF001_TST03
nosnap=on, nosnapdir=off, minra=off, no_atime_update=off, nvfail=off,
ignore_inconsistent=off, snapmirrored=off, create_ucode=on,
convert_ucode=off, 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=100, extent=off, try_first=volume_grow,
read_realloc=off, snapshot_clone_dependency=off

Filer> vol options OS_DUMP
nosnap=on, nosnapdir=on, minra=off, no_atime_update=off, nvfail=off,
ignore_inconsistent=off, snapmirrored=off, create_ucode=on,
convert_ucode=off, 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=100, extent=off, try_first=volume_grow,
read_realloc=off, snapshot_clone_dependency=off

Thanks,

Mohit.......

[dirkslechten]

This lun has already some vm's in it.

The lun is also protected with SMVI.

I Assume there is no problem turning the option on

[prakash_aviva]

This is an volume option and nothing to do with LUNs under it. by making it on, you are just making it hidden.

[dmorera]

Mohit is correct. All you are doing is hiding the snapshot directory (.snapshot) for that volume, regardless of what you have in the vol.

[lhoffman1]

you   mixep up snap reserve with  snap directory visibility ...   !

Filer> df -Vh GBRLON05VF001_TST03
Filesystem                total       used      avail capacity  Mounted on
/vol/GBRLON05VF001_TST03/      1024GB      156KB     1023GB       0%  /vol/GBRLON05VF001_TST03/
/vol/GBRLON05VF001_TST03/.snapshot       256GB        0KB      256GB       0%   /vol/GBRLON05VF001_TST03/.snapshot

Filer> df -Vh OS_DUMP
Filesystem                total       used      avail capacity  Mounted on
/vol/OS_DUMP/             100GB      144KB       99GB       0%  /vol/OS_DUMP/
snap  reserve               0KB        0KB        0KB     ---%   /vol/OS_DUMP/..

the above volume has a snap reserve >0  and the upper not  (0)  ..  thats the difference between both volumes !

regards

Lutz Hoffmann

[prakash_aviva]

Hi Lutz,

i was just showing the requestee abt the differnece in the volume options i.e. "nosnapdir"  option... which was the all abt the question asked.....