Przeglądaj źródła

devmapper: Do not check for transaction id during device metadata loading

Again, just because device transaction id is greater than pool transaction
id, it does not guarantee that device is in the pool. So do not check
of this during loading of device metadata.

Docker needs to deal with it. And device activation will fail when we try
to activate a device for whom metafile is present but there is no device
in the pool.

Signed-off-by: Vivek Goyal <vgoyal@redhat.com>
Vivek Goyal 10 lat temu
rodzic
commit
b721d6d8d0
1 zmienionych plików z 0 dodań i 5 usunięć
  1. 0 5
      daemon/graphdriver/devmapper/deviceset.go

+ 0 - 5
daemon/graphdriver/devmapper/deviceset.go

@@ -390,11 +390,6 @@ func (devices *DeviceSet) loadMetadata(hash string) *DevInfo {
 		return nil
 		return nil
 	}
 	}
 
 
-	// If the transaction id is larger than the actual one we lost the device due to some crash
-	if info.TransactionId > devices.TransactionId {
-		return nil
-	}
-
 	return info
 	return info
 }
 }