ONTAP Discussions

Delete data SVM root volume for LUN only environment

Chun_Chiang
1,953 Views

For a pure LUN environment by FC or iSCSI, is it ok to delete SVM root volume ?

 

Thanks,

Chun Chiang

1 ACCEPTED SOLUTION

Ontapforrum
1,918 Views

It's a good question. My observation is - Any Data SVM, serving NAS Protocols (CIFS/NFS), requires svm_root vol for Namespace hierarchy and also for in-heriting security style properties etc. However, for SAN (BLOCK only Protocols) this is not required. However, it's bit tricky.

1) If you have a running Data SVM with svm_root_vol and data vols, and if you plan to delete the svm_root_vol b'cos it's not required for SAN, it will not get deleted (even with force), I guess that's purely b'cos of the protection mechanism from Ontap.

 

2) However, if you have freshly created a new Data SVM, which automatically creates svm_root_vol, then you take it offline and delete it. It will not affect the SVM ability to start or stop. In this state, you can go ahead and create Data Volume (without the presence of svm_root_vol).

 

Therefore, if you happened to be in the 1st scenario, then you cannot get rid of of the svm_root_vol, b'cos it will complain "Cannot delete root volume because the Vserver has volumes."

 

I am quite intrigue to know why do you want to get rid of it ? , it hardly takes any space.

View solution in original post

3 REPLIES 3

Ontapforrum
1,919 Views

It's a good question. My observation is - Any Data SVM, serving NAS Protocols (CIFS/NFS), requires svm_root vol for Namespace hierarchy and also for in-heriting security style properties etc. However, for SAN (BLOCK only Protocols) this is not required. However, it's bit tricky.

1) If you have a running Data SVM with svm_root_vol and data vols, and if you plan to delete the svm_root_vol b'cos it's not required for SAN, it will not get deleted (even with force), I guess that's purely b'cos of the protection mechanism from Ontap.

 

2) However, if you have freshly created a new Data SVM, which automatically creates svm_root_vol, then you take it offline and delete it. It will not affect the SVM ability to start or stop. In this state, you can go ahead and create Data Volume (without the presence of svm_root_vol).

 

Therefore, if you happened to be in the 1st scenario, then you cannot get rid of of the svm_root_vol, b'cos it will complain "Cannot delete root volume because the Vserver has volumes."

 

I am quite intrigue to know why do you want to get rid of it ? , it hardly takes any space.

Chun_Chiang
1,902 Views

You explain it very clear. Removing root volume may simplify volume show output.
Do you know where LUN related info, such as igroup configuration, is stored ? Is it stored in SVM root volume ? 

Ontapforrum
1,860 Views

Ok. I am sure you can use filters in script to remove them from output. Coming to your query, LUN related info, or igroup configuration are  NOT stored in the SVM root volume.  LUN is created inside the volume, so it's metadata should be inside the volume. Regarding igroup, I don't know where it exactly it is stored, but you can create igroup even without a data volume. It's one of the vserver object.  

Public