Update disk_location_ec.go

When loadEcShards() fails partway through, some EC shards may already be loaded into the l.ecVolumes map in memory. The previous code only cleaned up filesystem files but left orphaned in-memory state, which could cause memory leaks and inconsistent state.

weed/storage/disk_location_ec.go

@@ -213,9 +213,13 @@ func (l *DiskLocation) loadAllEcShards() (err error) {
 			// If .dat is gone, log error but don't clean up (may be waiting for shards from other servers)
 			if datExists {
 				glog.Warningf("Failed to load EC shards for volume %d and .dat exists: %v, cleaning up EC files to use .dat...", volumeId, err)
+				// Clean up any partially loaded in-memory state before removing files
+				l.DestroyEcVolume(volumeId)
 				l.removeEcVolumeFiles(collection, volumeId)
 			} else {
 				glog.Warningf("Failed to load EC shards for volume %d: %v (this may be normal for distributed EC volumes)", volumeId, err)
+				// Clean up any partially loaded in-memory state even if we don't remove files
+				l.DestroyEcVolume(volumeId)
 			}
 			sameVolumeShards = nil
 			prevVolumeId = 0
@@ -226,7 +230,7 @@ func (l *DiskLocation) loadAllEcShards() (err error) {
 		continue
 	}
 
-	}
+}
 
 	// Check for orphaned EC shards without .ecx file (incomplete EC encoding)
 	// This happens when encoding is interrupted after writing shards but before writing .ecx