1
Bug reports / MD5 Checksum bug
« on: July 16, 2007, 04:09:46 AM »
I just switched a large folder with a lot of subfolders and files into a real-folder in the HFS interface. The program started generating md5 checksum files named .md5. The thing was, it started creating a new file for each new file, eg somefile.md5 had a file named somefile.md5.md5 created, and then somefile.md5.md5.md5, and then... well, you get the picture.
The fingerprints option shows disabled and I don't use md5 checksum files through HFS. This obviously filled my directories with worthless 32KB files (my cluster size) until I turned off and shutdown the server.
Any new information I get I'll post as I get it.
edit:
I now believe this to be a bug or lack of errortrap in the md5 checksum generation code. Disabling md5 checksum generation for files ending in .md5 would fix this immediately.
edit:
WORKAROUND
The menu shows the function is Disabled, but there's a checkmark next to save new calculated fingerprints. The filesize was set to 420.
I enabled fingerprints, cleared the checkmark, and reset the size to 0 to disable the function.
I searched for *.md5 on all my harddrives and deleted most of them, some i needed.
I'm back online now.
The fingerprints option shows disabled and I don't use md5 checksum files through HFS. This obviously filled my directories with worthless 32KB files (my cluster size) until I turned off and shutdown the server.
Any new information I get I'll post as I get it.
edit:
I now believe this to be a bug or lack of errortrap in the md5 checksum generation code. Disabling md5 checksum generation for files ending in .md5 would fix this immediately.
edit:
WORKAROUND
The menu shows the function is Disabled, but there's a checkmark next to save new calculated fingerprints. The filesize was set to 420.
I enabled fingerprints, cleared the checkmark, and reset the size to 0 to disable the function.
I searched for *.md5 on all my harddrives and deleted most of them, some i needed.
I'm back online now.