ONTAP Discussions
ONTAP Discussions
Maybe this is just in the ONTAP simulator, but after shrinking source and destination volumes (the latter through a snapmirror update) the 'vol size' on destination does not show the correct size (I followed the steps in KB29832 ), e.g. after shrinking volume testvolsrc from 110MB and a successful snapmirror update, I see:
On source: vol size testvolsrc: vol size: Flexible volume 'voltestsrc' has size 100m.
On destination: vol size testvol: vol size: Flexible volume 'voltest' has size 110m.
FilerView, df etc on destination does show the correct size in destination volume 'testvol'.
Did I overlook something - has anybody of you an idea?
Kind regards,
Soren
You need to break the snapmirror and resize the destination manually, then resync the snapmirror
that is my experience - I'd like to know if there is a better way!
Hi,
This might seem counter-intuitive, but the sizes of the destination volume for volume snapmirror will always "look" the same if the destination is of equal size (+ a few MB) or larger, no matter what the actual size is. You need to use vol size -b (if I remember correctly) to get the actual size of the destination volume. You can always resize the destination volume manually, but if you go below the source volume size (or adjust the source to be larger than the destination) the mirror won't update. So if you want to adjust the test volume down a bit, then just 'vol size testvol 112m' and you're done.
Its vol status -b
Volume Block Size (bytes) Vol Size (blocks) FS Size (blocks)
------ ------------------ ------------------ ----------------
vol0 4096 25952256 25952256
net2 4096 684510413 590558004
sg12 4096 8912896 8650752
web2 4096 14417920 13107200
backup1 4096 5242880 3932160
data 4096 15204352 14417920
vm2 4096 667942912 563714458
archive 4096 418906112 402653184
65net 4096 275251200 251658240
fcappdata 4096 18350080 14417920
appdata 4096 367001600 348966093
net5 4096 216006656 183500800
backup2 4096 443862221 322122548