2017-01-20 12:36 PM
I used volumeGetIter API to tyr to see if the C-mode volume can be identified as NFS vlome or FC block volume. I do not see any filed I can use to indentify the volume type.
Solved! SEE THE SOLUTION
2017-01-20 12:55 PM
There's no difference at the volume level between "block" and "file" FlexVols. A "block" volume is simply a FlexVol that contains a LUN.
So, there is no single API call which can determine if the volume is being used for block or file access. Instead it's checking to see which protocols are enabled for the volume using the appropriate APIs.
Hope that helps.
2017-01-20 01:09 PM
Thanks for the quick response!
Is this statement true: a volume is what you map to for CIFS/NTFS, ie a file share, and a LUN is what you map to when using block-level services on the filer.
I thought vloume can be both NFS and block and lun can only be used as block storage.
2017-01-20 02:13 PM
Volumes are necessary in ONTAP regardless of protocol. With SMB/CIFS/NFS the data is stored directly in the volume as files. With iSCSI/FC/FCoE a LUN is created (which is also a file) in the volume and the clients connect to that LUN and place a file system on it.
Having a volume which has LUN inside it and has SMB/CIFS/NFS access is dangerous because the LUN (remember, it's a file to WAFL) could potentially be manipulated through the file protocol.
2017-01-22 07:40 AM