Hi,
maybe someone else has this issue?
Two of my testlab datasets show "nonconformant" every couple of minutes and generate alarms. These datasets use a "thin/nofat san" provisioning policy (no guarantee, no space reserve).
The NMC "Conform Now" says it needs to disable the lun space reserv, and a manual conformance run solves it, dataset goes "conformant", but at next monitoring interval, the same thing happens again - nonconformant and wanting to turn the lun reservation off...
I get these errors in DFM 40D15 conformance log:
Oct 18 22:24:44 [dfmserver:DEBUG]: [532:0x90c]: Conformance checker started scanning at Mon Oct 18 22:24:43 2010
Oct 18 22:24:44 [dfmserver:DEBUG]: [532:0x90c]: Finished scanning dataset UCN Testlab dmotionVMDS with protection policy: UNPROTECTED, unresolvable tasks: 0, resolvable tasks: 0, resolvable-need confirm tasks: 1
Oct 18 22:41:09 [dfmserver:ERROR]: [532:0xb04]: VolLUNSpaceReserveValidate::handle_error(): Volume dmotionSAN:/dmotionSAN (115905) has failed lun-space-reservation validation. Error Code: 141 Reason: This volume's lun-space-reservation option value does not match the policy option values Suggestion: Set lun-space-reservation option as per policy option values.
Oct 18 22:41:09 [dfmserver:DEBUG]: [532:0xb04]: Conformance checker started scanning at Mon Oct 18 22:41:09 2010
Oct 18 22:41:09 [dfmserver:DEBUG]: [532:0xb04]: Finished scanning dataset UCN Testlab dmotionSAN with protection policy: UNPROTECTED, unresolvable tasks: 0, resolvable tasks: 0, resolvable-need confirm tasks: 1
Oct 18 22:41:16 [dfmserver:ERROR]: [532:0xd80]: VolLUNSpaceReserveValidate::handle_error(): Volume dmotionVMDS:/dmotionVMDS (117344) has failed lun-space-reservation validation. Error Code: 141 Reason: This volume's lun-space-reservation option value does not match the policy option values Suggestion: Set lun-space-reservation option as per policy option values.
Oct 18 22:41:16 [dfmserver:DEBUG]: [532:0xd80]: Conformance checker started scanning at Mon Oct 18 22:41:15 2010
Oct 18 22:41:16 [dfmserver:DEBUG]: [532:0xd80]: Finished scanning dataset UCN Testlab dmotionVMDS with protection policy: UNPROTECTED, unresolvable tasks: 0, resolvable tasks: 0, resolvable-need confirm tasks: 1
Oct 18 22:57:37 [dfmserver:ERROR]: [532:0xf0c]: VolLUNSpaceReserveValidate::handle_error(): Volume dmotionSAN:/dmotionSAN (115905) has failed lun-space-reservation validation. Error Code: 141 Reason: This volume's lun-space-reservation option value does not match the policy option values Suggestion: Set lun-space-reservation option as per policy option values.
Oct 18 22:57:37 [dfmserver:DEBUG]: [532:0xf0c]: Conformance checker started scanning at Mon Oct 18 22:57:37 2010
Oct 18 22:57:37 [dfmserver:DEBUG]: [532:0xf0c]: Finished scanning dataset UCN Testlab dmotionSAN with protection policy: UNPROTECTED, unresolvable tasks: 0, resolvable tasks: 0, resolvable-need confirm tasks: 1
Oct 18 22:57:44 [dfmserver:ERROR]: [532:0xb04]: VolLUNSpaceReserveValidate::handle_error(): Volume dmotionVMDS:/dmotionVMDS (117344) has failed lun-space-reservation validation. Error Code: 141 Reason: This volume's lun-space-reservation option value does not match the policy option values Suggestion: Set lun-space-reservation option as per policy option values.
Oct 18 22:57:45 [dfmserver:DEBUG]: [532:0xb04]: Conformance checker started scanning at Mon Oct 18 22:57:44 2010
Oct 18 22:57:45 [dfmserver:DEBUG]: [532:0xb04]: Finished scanning dataset UCN Testlab dmotionVMDS with protection policy: UNPROTECTED, unresolvable tasks: 0, resolvable tasks: 0, resolvable-need confirm tasks: 1
The filer LUN within this vFilers's volume is definitely NOT space reserved, and has never been:
dmotionSAN@filer9> vol status -v dmotionSAN
Volume State Status Options
dmotionSAN online raid_dp, flex nosnap=on, nosnapdir=off,
redirect minra=off, no_atime_update=on,
nvfail=off,
ignore_inconsistent=off,
snapmirrored=off,
create_ucode=on,
convert_ucode=on,
maxdirsize=18350,
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=on,
fractional_reserve=100,
extent=off,
try_first=volume_grow,
read_realloc=off,
snapshot_clone_dependency=on
Containing aggregate: 'aggr0'
Plex /aggr0/plex0: online, normal, active
RAID group /aggr0/plex0/rg0: normal
Snapshot autodelete settings for dmotionSAN:
state=on
commitment=destroy
trigger=volume
target_free_space=5%
delete_order=oldest_first
defer_delete=prefix
prefix=dfpm
destroy_list=lun_clone,vol_clone,cifs_share
Volume autosize settings:
state=off
dmotionSAN@filer9> lun show -v
/vol/dmotionSAN/o10g_lun0/o10g_lun0 40.0g (42953867264) (r/w, online, mapped)
Serial#: P3I4dZZTXv1j
Share: none
Space Reservation: disabled
Multiprotocol Type: linux
Maps: dfpm_dmotionSAN=0
It is just like it was created by ProvMgr.
The CLI on DFM server shows:
C:\>dfpm dataset conform -D 115778
Dataset dry run results
----------------------------------
Do: Disable space reservation for LUN dmotionSAN:/dmotionSAN/o10g_lun0/o10g_lun0
Effect: Disable space reservation of the LUN.
I also found:
C:\> dfpm dataset get 115778
Allow custom volume settings on provisioned volumes: No
Enable periodic write guarantee checks on SAN datasets: No
But however I try to set this option, it does not do anything:
C:\>dfpm dataset set 115778 isEnableWGChecks=Never
Left settings unchanged for 115778.
C:\>dfpm dataset set 115778 isEnableWGChecks=No
Left settings unchanged for 115778.
C:\>dfpm dataset set 115778 isEnableWGChecks=Yes
Left settings unchanged for 115778.
C:\>dfpm dataset set 115778 isEnableWGChecks=On
Left settings unchanged for 115778.
These 2 datasets toggle to nonconformant all the time since I performed datamotion on them in the past (successfully and cleand up).
They have been fine before the first datamotion (nondisruptive migration) operation AFAICT.
Ideas, anyone?
