Skip to content

Commit e7cd8f6

Browse files
adarshv98roygara
andauthored
Update articles/storage/elastic-san/elastic-san-delete.md
Co-authored-by: rogara <[email protected]>
1 parent 09b182c commit e7cd8f6

File tree

1 file changed

+0
-1
lines changed

1 file changed

+0
-1
lines changed

articles/storage/elastic-san/elastic-san-delete.md

Lines changed: 0 additions & 1 deletion
Original file line numberDiff line numberDiff line change
@@ -64,7 +64,6 @@ iscsiadm --mode node --target **yourStorageTargetIQN** --portal **yourStorageTar
6464

6565
When your SAN has no active connections to any clients, you may delete it using the Azure portal or Azure PowerShell module. If you delete a SAN or a volume group, the corresponding child resources will be deleted along with it. The delete commands for each of the resource levels are below.
6666

67-
One thing to note about the SAN deletion process is that if you have not deleted all the volumes that have active iSCSI connections, the delete operation will delete all the volumes that don't have iSCSI connections but will fail on those volumes that do, and the SAN, volume groups, and volumes with active iSCSI connections will remain. Similarly, deleting volumes that have active iSCSI connections will cause the delete operation to fail. If you want to delete a volume, you must delete any active iSCSI connections it may have.
6867

6968
To delete volumes, run the below commands.
7069

0 commit comments

Comments
 (0)