I can not find any reference to this message. I know it is only classed as “info” but the message suggest something is miss-configured.
filer104> Sat Oct 31 19:27:05 GMT [app.log.info:info]: WIN2003-SNAPDRI: SnapDrive 6.1: (373) Service execution status: Found non-space reserved LUN(s) on volume '/vol/win2003_sd_01'. This volume is not designated for thin provisioning.
The volume on the filer has a guarantee of “none” and the LUN does not have space reserve enabled (by using storacl.exe).
It has taken me a while to get back to testing this but I have and I cannot see why the message is being produced and I am thinking it is a bug.
Using SD6.1 and 7.3.1 Sim (although I originally saw the issue on a live 7.3.1 filer) I can create the "This volume is not designated for thin provisioning" message when both the LUN has its Space Reservation parameter set to "false" and the "ThinProvision.xml" file has the volume set with the space_reservation_new_lun parameter to “false” (set via the spacereserve set command it STORACL, and as per kb47898). When these two parameters are set (which they would be if you create a new LUN via SD once you have used STORACL to set spacereserve to false) and either you restart the server or just restart the SnapDrive service the filer reports the "This volume is not designated for thin provisioning" message in the console. It does not seem to matter how the volume is set up, fat, thin, autosize enabled etc just the aforementioned two parameters.
I did check the tr-3483.pdf and specifically section 7.3 but as I expected the "sdparams.conf" file is now superseded by the STORACL command and therefore the values in the “sdparams.conf” file have no barring.
Therefore I think it is a bug that the message is created as I believe both the LUNs and volumes are setup correctly, Watan could you pass this onto the SnapDrive development team?
I was able to confirm with the engineering team that they are aware of this issue. They have linked this issue with another burt 313750 and will work to get this resolved in a patch or the next release. This will be decided in the weeks to come.