Menu
▾
▴
s3tools-general
|
From: Ryan G. <ngs...@gm...> - 2012-10-17 15:15:46
|
Hi - I'm using the get function in 1.1.0-beta3. When I download data from s3 using get, s3cmd reports the md5 doesn't match. However, when I check myself, it matches. The error I get is something like: WARNING: MD5 signatures do not match: computed=d91f7cabb9a83b6ea446e166b5e838a5, received="76a74a3a4245f2898ce09d1cf89b1eae-423" This is a problem because I need to upload an md5 file with each file and check them manually. Why am I getting this? |
|
From: William s. <w_...@co...> - 2012-10-17 16:27:01
|
Yeah, known problem, no fix. It also breaks the sync functions. Trying to remember if it's files over a certain size that get the different format of md5 ... William P.N. Smith ComputerSmiths Consulting, Inc. On Oct 17, 2012, at 11:15 AM, Ryan Golhar <ngs...@gm...> wrote: > Hi - I'm using the get function in 1.1.0-beta3. When I download data from s3 using get, s3cmd reports the md5 doesn't match. However, when I check myself, it matches. The error I get is something like: > > WARNING: MD5 signatures do not match: computed=d91f7cabb9a83b6ea446e166b5e838a5, received="76a74a3a4245f2898ce09d1cf89b1eae-423" > > This is a problem because I need to upload an md5 file with each file and check them manually. Why am I getting this? > ------------------------------------------------------------------------------ > Everyone hates slow websites. So do we. > Make your web apps faster with AppDynamics > Download AppDynamics Lite for free today: > http://p.sf.net/sfu/appdyn_sfd2d_oct > _______________________________________________ > S3tools-general mailing list > S3t...@li... > https://lists.sourceforge.net/lists/listinfo/s3tools-general |
|
From: William S. <w_...@co...> - 2013-05-20 16:17:51
|
I assume this version for sorting out MD5SUM is going to be in the new release? Thanks! On Oct 17, 2012, at 12:04 PM, Matt_Domsch@Dell.com wrote: > If the file is bigger than the chunk size, you’ll need a version (e.g. from my github merge branch) that stores the real MD5SUM in the metadata, rather than relying on the S3 ETag, which is incorrect if using it to compare the whole file – the S3 ETag only is correct for a single chunk of the file. > > -- > Matt Domsch > Technology Strategist > Dell | Office of the CTO > <image001.jpg> > > From: Ryan Golhar [mailto:ngs...@gm...] > Sent: Wednesday, October 17, 2012 8:16 AM > To: s3t...@li... > Subject: [S3tools-general] md5 doesn't match > > Hi - I'm using the get function in 1.1.0-beta3. When I download data from s3 using get, s3cmd reports the md5 doesn't match. However, when I check myself, it matches. The error I get is something like: > > WARNING: MD5 signatures do not match: computed=d91f7cabb9a83b6ea446e166b5e838a5, received="76a74a3a4245f2898ce09d1cf89b1eae-423" > > This is a problem because I need to upload an md5 file with each file and check them manually. Why am I getting this? > ------------------------------------------------------------------------------ > Everyone hates slow websites. So do we. > Make your web apps faster with AppDynamics > Download AppDynamics Lite for free today: > http://p.sf.net/sfu/appdyn_sfd2d_oct_______________________________________________ > S3tools-general mailing list > S3t...@li... > https://lists.sourceforge.net/lists/listinfo/s3tools-general |
|
From: Matt D. <ma...@do...> - 2013-05-20 16:25:06
|
On Mon, May 20, 2013 at 11:17 AM, William Smith <w_...@co...>wrote: > I assume this version for sorting out MD5SUM is going to be in the new > release? > > Thanks! > > On Oct 17, 2012, at 12:04 PM, Matt_Domsch@Dell.com wrote: > > > If the file is bigger than the chunk size, you’ll need a version (e.g. > from my github merge branch) that stores the real MD5SUM in the metadata, > rather than relying on the S3 ETag, which is incorrect if using it to > compare the whole file – the S3 ETag only is correct for a single chunk of > the file. > Yes, these patches are in 1.5.0-alpha already. |
|
From: Matt D. <ma...@do...> - 2013-05-21 02:12:03
|
On Mon, May 20, 2013 at 11:24 AM, Matt Domsch <ma...@do...> wrote: > On Mon, May 20, 2013 at 11:17 AM, William Smith <w_...@co...>wrote: > >> I assume this version for sorting out MD5SUM is going to be in the new >> release? >> >> Thanks! >> >> On Oct 17, 2012, at 12:04 PM, Matt_Domsch@Dell.com wrote: >> >> > If the file is bigger than the chunk size, you’ll need a version (e.g. >> from my github merge branch) that stores the real MD5SUM in the metadata, >> rather than relying on the S3 ETag, which is incorrect if using it to >> compare the whole file – the S3 ETag only is correct for a single chunk of >> the file. >> > > > Yes, these patches are in 1.5.0-alpha already. > > Though I found a bug with them today. We weren't always looking for the md5 value from the headers where we should - specifically the sync recursive case without wildcards. This is fixed now in my merge branch. https://github.com/mdomsch/s3cmd/tree/merge |
Thanks for helping keep SourceForge clean.
X