2010-09-27 03:10 AM
I'm pretty new on this forum, so I hope I'm posting this in right place. I've created a volume, one lun inside and I'm having a problem that volume seems full. But, according to my logic there should be some space free.
NAS-SC-01-B> vol status
Volume State Status Options
vol0 online raid_dp, flex root, create_ucode=on
VM_SYSTEM online raid_dp, flex create_ucode=on
VM_DATA_B online raid_dp, flex create_ucode=on
NAS-SC-01-B> df -h VM_SYSTEM
Filesystem total used avail capacity Mounted on
/vol/VM_SYSTEM/ 950GB 950GB 0GB 100% /vol/VM_SYSTEM/
/vol/VM_SYSTEM/.snapshot 50GB 150MB 49GB 0% /vol/VM_SYSTEM/.snapshot
NAS-SC-01-B> df -s VM_SYSTEM
Filesystem used saved %saved
/vol/VM_SYSTEM/ 996147200 0 0%
NAS-SC-01-B> lun show
/vol/VM_DATA_B/lun0 239.0g (256647364608) (r/w, online, mapped)
/vol/VM_SYSTEM/lun0 805.0g (864406208512) (r/w, online, mapped)
I'm unable to raise snapshot reserved space:
NAS-SC-01-B> snap reserve VM_SYSTEM 6
snap reserve: Not enough space to set the desired percentage.
Snapshot operation failed: No space left on device.
What am I doing wrong?
2010-09-27 03:43 AM
So, after starting a deduplication process manualy I got:
Mon Sep 27 12:22:39 CEST [NAS-SC-01-B: wafl.snap.delete:info]: Snapshot copy sis.ef5f6ee0-cb2d-11df-966d-00a09824ff5c on volume VM_SYSTEM NetApp was deleted.
Mon Sep 27 12:22:39 CEST [NAS-SC-01-B: wafl.vol.full:notice]: file system on volume VM_SYSTEM is full
Mon Sep 27 12:22:39 CEST [NAS-SC-01-B: sis.op.aborted:error]: SIS operation for /vol/VM_SYSTEM has aborted: Not enough disk space for the operation
Mon Sep 27 12:22:39 CEST [NAS-SC-01-B: sis.cfg.setFailed:error]: Saving SIS volume configuration for volume /vol/VM_SYSTEM :Not enough disk space for the operation
2010-09-27 04:45 AM
Couple of things to check
What are the options for that volume? run vol options <vol_name>
My guess is that space guarantee is set to volume and fractional reserve is at 100%
Also is what is the space reservation set to on the lun? lun set reservation <lun_name> to see what that is.
In both cases my preference is to set the volume space guarantee to none and lun reservation to disabled. Thin provisioned
Also I do not use a snap reserve on volumes containing luns just have the volumes sized larger than the lun to hold the snapshots. This can depend on alot of factors some of the volumes are 20% bigger than the lun while some are 150% bigger it just depends on the change rate of the blocks.
To set the volume guarantee to none, run. vol options <vol_name> guarantee none
To set the lun reservation, run. lun set reservation <lun_name> disable
After those are set you should be able to run sis to deduplicate the volume