trying to word this with as much respect as possible to my favorite project: the use of checksums on volumes is either half baked or degraded. A more strict check or at more places could be concocted but I guess no one has a good enough use case for it to actually go do it. I don't know the use cases implemented but for the download-with-checksum one. One that is not implemented is for checking the move to zones of templates. I am very interested in it if someone is having the full picture.
Op do 7 mei 2015 om 10:59 schreef Jan-Arve Nygård <jan.arve.nyg...@gmail.com >: > Hi, > > I'm seeing that md5sum is being run for every volume upload, even if no > checksum is specified during upload. > > The checksum value in volume_store_ref is null but "md5sum -c --status" > seems to run for every upload on SSVM. No checksum seems to be written to > the table afterwards either but it seems to be written to a > volume.properties file on secondary storage. > > I see that installvolume.sh is invoked with the checksum specified and i > wonder if this is necessary when the volume was uploaded without a checksum > if the first place and the VHD is already on the same storage. This could > save some time during upload of volumes, especially with large ones. > > Does anyone know this upload/installation procedure better and maybe have a > good explanation of this behavior? Am i misunderstanding something here > maybe? > > -thinktwo >