Moodle
  1. Moodle
  2. MDL-27137

Incorrect content of hash pool file

    Details

    • Database:
      MySQL
    • Difficulty:
      Moderate
    • Affected Branches:
      MOODLE_20_STABLE, MOODLE_22_STABLE
    • Rank:
      16778

      Description

      I was trying to add a new scorm activity, using the same file with a different name (current.zip and current_new.zip, for example), from a repository I have, but moodle doesn't allow me deploy the package (see attached screenshot)

      I checked the "files" table and both files have the same contenthash, what I suspect may be the problem.

      This issue was also reported here http://moodle.org/mod/forum/discuss.php?d=164323 but with a different approach (backup)

      1. mdl-27137.diff
        0.5 kB
        Matt Oquist
      1. scorm_hashpool_majorbug.png
        8 kB

        Issue Links

          Activity

          Hide
          Luis de Vasconcelos added a comment -

          I'm experiencing the same problem upgrading a 1.9.10+ (Build: 20110112) site to version 2.0.3+ (Build: 20110511).

          I traced it down to a file called D:\MoodleData\filedir\91\b7\91b75477f04e8186413828618bd9e09e2c2203ca which is a 81,068 KB file! I don't know what it is!

          My PHP PHPErrors.log file has this info:

          [16-May-2011 08:56:22] Default exception handler: Incorrect pool file content 91b75477f04e8186413828618bd9e09e2c2203ca. Debug:

          • line 1062 of \lib\filestorage\file_storage.php: file_pool_content_exception thrown
          • line 810 of \lib\filestorage\file_storage.php: call to file_storage->add_file_to_pool()
          • line 337 of \lib\db\upgradelib.php: call to file_storage->create_file_from_pathname()
          • line 360 of \lib\db\upgradelib.php: call to upgrade_migrate_files_course()
          • line 98 of \lib\db\upgradelib.php: call to upgrade_migrate_files_course()
          • line 593 of \lib\db\upgrade.php: call to upgrade_migrate_files_courses()
          • line 1382 of \lib\upgradelib.php: call to xmldb_main_upgrade()
          • line 273 of \admin\index.php: call to upgrade_core()

          I don't have any scorm content in any of my courses.

          These related 'Using Moodle' forum discussions don't have any workable solutions: http://moodle.org/mod/forum/discuss.php?d=172909
          http://moodle.org/mod/forum/discuss.php?d=163074

          Show
          Luis de Vasconcelos added a comment - I'm experiencing the same problem upgrading a 1.9.10+ (Build: 20110112) site to version 2.0.3+ (Build: 20110511). I traced it down to a file called D:\MoodleData\filedir\91\b7\91b75477f04e8186413828618bd9e09e2c2203ca which is a 81,068 KB file! I don't know what it is! My PHP PHPErrors.log file has this info: [16-May-2011 08:56:22] Default exception handler: Incorrect pool file content 91b75477f04e8186413828618bd9e09e2c2203ca. Debug: line 1062 of \lib\filestorage\file_storage.php: file_pool_content_exception thrown line 810 of \lib\filestorage\file_storage.php: call to file_storage->add_file_to_pool() line 337 of \lib\db\upgradelib.php: call to file_storage->create_file_from_pathname() line 360 of \lib\db\upgradelib.php: call to upgrade_migrate_files_course() line 98 of \lib\db\upgradelib.php: call to upgrade_migrate_files_course() line 593 of \lib\db\upgrade.php: call to upgrade_migrate_files_courses() line 1382 of \lib\upgradelib.php: call to xmldb_main_upgrade() line 273 of \admin\index.php: call to upgrade_core() I don't have any scorm content in any of my courses. These related 'Using Moodle' forum discussions don't have any workable solutions: http://moodle.org/mod/forum/discuss.php?d=172909 http://moodle.org/mod/forum/discuss.php?d=163074
          Hide
          Luis de Vasconcelos added a comment -

          Running this query does not return any results:
          SELECT * FROM mdl_files WHERE contenthash = '91b75477f04e8186413828618bd9e09e2c2203ca';

          My site is running on this platform:

          Windows Server 2003 Standard Edition (Build 3790: Service Pack 2)
          Intel Xeon CPU 5120 @ 1.86GHz 512MB RAM
          IIS 6.0.3790.4735
          Microsoft SQL Server 2005 - 9.00.4053.00 (Intel X86) Standard Edition
          PHP 5.3.3 NTS VC9
          PHP date.timezone = "Africa/Johannesburg"
          Microsoft FastCGI Handler x86 6.1.36.1
          Microsoft SQL Server Driver for PHP 2.0.1802.200
          Microsoft Windows Cache Extension for PHP 1.1.630.0

          Moodle config:
          $CFG->dbtype = 'sqlsrv';
          $CFG->dblibrary = 'native';

          Show
          Luis de Vasconcelos added a comment - Running this query does not return any results: SELECT * FROM mdl_files WHERE contenthash = '91b75477f04e8186413828618bd9e09e2c2203ca'; My site is running on this platform: Windows Server 2003 Standard Edition (Build 3790: Service Pack 2) Intel Xeon CPU 5120 @ 1.86GHz 512MB RAM IIS 6.0.3790.4735 Microsoft SQL Server 2005 - 9.00.4053.00 (Intel X86) Standard Edition PHP 5.3.3 NTS VC9 PHP date.timezone = "Africa/Johannesburg" Microsoft FastCGI Handler x86 6.1.36.1 Microsoft SQL Server Driver for PHP 2.0.1802.200 Microsoft Windows Cache Extension for PHP 1.1.630.0 Moodle config: $CFG->dbtype = 'sqlsrv'; $CFG->dblibrary = 'native';
          Hide
          Luis de Vasconcelos added a comment -

          I tried upgrading the 1.9.10+ (Build: 20110112) site to version 2.0.2+ (Build: 20110427) and I get the same "Incorrect pool file content" error.

          So I guess there's a "bad file" somewhere in one of my courses.

          How do I identify what that D:\MoodleData\filedir\91\b7\91b75477f04e8186413828618bd9e09e2c2203ca file is?

          Show
          Luis de Vasconcelos added a comment - I tried upgrading the 1.9.10+ (Build: 20110112) site to version 2.0.2+ (Build: 20110427) and I get the same "Incorrect pool file content" error. So I guess there's a "bad file" somewhere in one of my courses. How do I identify what that D:\MoodleData\filedir\91\b7\91b75477f04e8186413828618bd9e09e2c2203ca file is?
          Hide
          Walter Draffin, Jr added a comment -

          If you look at the bottom of this thread at my post, you will see some more details on the backup/restore issue.

          http://moodle.org/mod/forum/discuss.php?d=163074

          Show
          Walter Draffin, Jr added a comment - If you look at the bottom of this thread at my post, you will see some more details on the backup/restore issue. http://moodle.org/mod/forum/discuss.php?d=163074
          Hide
          Nick Freeman added a comment -

          We experienced a similar problem when upgrading from 1.9.12 to 2.1 in a windows environment. All system checks were OK, but then, after about 30 seconds (without going to the upgrade page with the % bars), we got the message "Site is being upgraded, please retry later".

          The upgrade did appear to have worked fine in terms of code (definitely lookedlike 2.1 code!) and database (300 tables in the schema) but nothing had happened with the files.

          We had previously managed a successful upgrade on a staging server, with the same windows environment setup. However, afterwards, we realised that we had done this with an empty moodledata folder; hence the reasoning that it was a file migration error.

          However, as we had a recent copy of the 1.9.12 site on a linux machine, we tried the upgrade there and it worked fine.

          The windows environment was:

          • PHP5.3.6
          • mysql 5.0.8
          • IIS 7

          The linux environment was:

          • PHP 5.3.2-1ubuntu4.9
          • mysql 5.1.41, for debian-linux-gnu (i486)
          • Apache/2.2.14 (Ubuntu)

          Hope that helps

          Show
          Nick Freeman added a comment - We experienced a similar problem when upgrading from 1.9.12 to 2.1 in a windows environment. All system checks were OK, but then, after about 30 seconds (without going to the upgrade page with the % bars), we got the message "Site is being upgraded, please retry later". The upgrade did appear to have worked fine in terms of code (definitely lookedlike 2.1 code!) and database (300 tables in the schema) but nothing had happened with the files. We had previously managed a successful upgrade on a staging server, with the same windows environment setup. However, afterwards, we realised that we had done this with an empty moodledata folder; hence the reasoning that it was a file migration error. However, as we had a recent copy of the 1.9.12 site on a linux machine, we tried the upgrade there and it worked fine. The windows environment was: PHP5.3.6 mysql 5.0.8 IIS 7 The linux environment was: PHP 5.3.2-1ubuntu4.9 mysql 5.1.41, for debian-linux-gnu (i486) Apache/2.2.14 (Ubuntu) Hope that helps
          Hide
          Walter Draffin, Jr added a comment -

          We just tried doing an import and received the same error as mentioned in my post here http://moodle.org/mod/forum/discuss.php?d=163074

          Show
          Walter Draffin, Jr added a comment - We just tried doing an import and received the same error as mentioned in my post here http://moodle.org/mod/forum/discuss.php?d=163074
          Hide
          Richard Lang added a comment -

          I think this issue needs urgent attention. We are having problems adding a SCORM activity to a course. We can select the SCORM file, but as soon as we click 'Save and return to course', we get the error 'Incorrect pool file content'. The long string of characters in the error is traceable back to a specific file created in moodledata/filedir.

          We also get the error intimitently when trying to upload other files such as gif files or png's to profile pics. I have also tried creating a very small SCORM activity with only HTML files within it, but it makes not difference.

          I have tried on two different shared hosts, one with a custom theme, and one with a fresh install. Not migration or backing up, just installing Moodle 2.1 and trying to upload a file.

          This is more than a backup/restore issue... it seems to be a filedir issue in Moodle 2.1

          Show
          Richard Lang added a comment - I think this issue needs urgent attention. We are having problems adding a SCORM activity to a course. We can select the SCORM file, but as soon as we click 'Save and return to course', we get the error 'Incorrect pool file content'. The long string of characters in the error is traceable back to a specific file created in moodledata/filedir. We also get the error intimitently when trying to upload other files such as gif files or png's to profile pics. I have also tried creating a very small SCORM activity with only HTML files within it, but it makes not difference. I have tried on two different shared hosts, one with a custom theme, and one with a fresh install. Not migration or backing up, just installing Moodle 2.1 and trying to upload a file. This is more than a backup/restore issue... it seems to be a filedir issue in Moodle 2.1
          Hide
          Xavier Paz added a comment -

          I've experienced it again, still related with scorm but in a different situation. I had a SCORM activiy already created, but when I selected the same zip to deploy all again in the same course, Moodle showed the same "incorrect hash pool" message and then, I can't deploy the same zip in other courses along the platform.

          I agree with Richard, the issue really needs urgent attention.

          Show
          Xavier Paz added a comment - I've experienced it again, still related with scorm but in a different situation. I had a SCORM activiy already created, but when I selected the same zip to deploy all again in the same course, Moodle showed the same "incorrect hash pool" message and then, I can't deploy the same zip in other courses along the platform. I agree with Richard, the issue really needs urgent attention.
          Hide
          Walter Draffin, Jr added a comment -

          I fixed our installation. I was using the BigBlueButton plugin and it was causing the problem. I deleted that plugin and removed the folder from the mod folder, and all issues are fixed.

          Show
          Walter Draffin, Jr added a comment - I fixed our installation. I was using the BigBlueButton plugin and it was causing the problem. I deleted that plugin and removed the folder from the mod folder, and all issues are fixed.
          Hide
          sschafft added a comment -

          I am having a similar issue. I think this might have to do with the SCORM size. The SCORM package I was given to use was 190MB, the file size upload limit is 256MB (set in PHP) . The course uploads fine as a file, however if I add it as a SCORM package it fails and I get a "incorrect hash pool" message. All other SCORM packages work at smaller sizes.

          I am running 2.0.6 Build 20111205 on a shared hosting environment that is based on Debian Linux.

          Error / Stack Trace:

          "Incorrect pool file content b3f9a14348ccbb8d30a176118129358457ae137b."

          Stack trace:
          line 1149 of /lib/filestorage/file_storage.php: file_pool_content_exception thrown
          line 951 of /lib/filestorage/file_storage.php: call to file_storage->add_string_to_pool()
          line 353 of /lib/filestorage/zip_packer.php: call to file_storage->create_file_from_string()
          line 217 of /lib/filestorage/stored_file.php: call to zip_packer->extract_to_storage()
          line 214 of /mod/scorm/locallib.php: call to stored_file->extract_to_storage()
          line 118 of /mod/scorm/lib.php: call to scorm_parse()
          line 410 of /course/modedit.php: call to scorm_add_instance()

          Any ideas would be extremely helpful....

          Show
          sschafft added a comment - I am having a similar issue. I think this might have to do with the SCORM size. The SCORM package I was given to use was 190MB, the file size upload limit is 256MB (set in PHP) . The course uploads fine as a file, however if I add it as a SCORM package it fails and I get a "incorrect hash pool" message. All other SCORM packages work at smaller sizes. I am running 2.0.6 Build 20111205 on a shared hosting environment that is based on Debian Linux. Error / Stack Trace: "Incorrect pool file content b3f9a14348ccbb8d30a176118129358457ae137b." Stack trace: line 1149 of /lib/filestorage/file_storage.php: file_pool_content_exception thrown line 951 of /lib/filestorage/file_storage.php: call to file_storage->add_string_to_pool() line 353 of /lib/filestorage/zip_packer.php: call to file_storage->create_file_from_string() line 217 of /lib/filestorage/stored_file.php: call to zip_packer->extract_to_storage() line 214 of /mod/scorm/locallib.php: call to stored_file->extract_to_storage() line 118 of /mod/scorm/lib.php: call to scorm_parse() line 410 of /course/modedit.php: call to scorm_add_instance() Any ideas would be extremely helpful....
          Hide
          Virgil Ashruf added a comment -

          This problem also still occurs in one of our 2.2.1 installation (build 20120202)

          I copied this from our error_log

          When opening a SCORM activity which was already in place:
          [Wed Mar 14 09:51:58 2012] [error] [client 83.163.190.138] Default exception handler: Het gevraagde bestand is niet gevonden Debug: \n* line 435 of /lib/setuplib.php: moodle_exception thrown\n* line 1568 of /lib/filelib.php: call to print_error()\n* line 3860 of /lib/filelib.php: call to send_file_not_found()\n* line 37 of /pluginfile.php: call to file_pluginfile()\n, referer: http://our.2.2.1.installation/mod/scorm/loadSCO.php?a=183&scoid=531&currentorg=WIE5_6755399441055843_nl_Content&attempt=1

          When trying to add a new SCORM activity
          [Wed Mar 14 09:54:58 2012] [error] [client 83.163.190.138] Default exception handler: Foute inhoud pool-bestand 3213c0f4244e63cb1a1ce86e277d74da6160566c. Debug: \n* line 1163 of /lib/filestorage/file_storage.php: file_pool_content_exception thrown\n* line 959 of /lib/filestorage/file_storage.php: call to file_storage->add_string_to_pool()\n* line 353 of /lib/filestorage/zip_packer.php: call to file_storage->create_file_from_string()\n* line 217 of /lib/filestorage/stored_file.php: call to zip_packer->extract_to_storage()\n* line 229 of /mod/scorm/locallib.php: call to stored_file->extract_to_storage()\n* line 126 of /mod/scorm/lib.php: call to scorm_parse()\n* line 443 of /course/modedit.php: call to scorm_add_instance()\n, referer: http://our.2.2.1.installation/course/modedit.php?add=scorm&type=&course=199&section=1&return=0

          Show
          Virgil Ashruf added a comment - This problem also still occurs in one of our 2.2.1 installation (build 20120202) I copied this from our error_log When opening a SCORM activity which was already in place: [Wed Mar 14 09:51:58 2012] [error] [client 83.163.190.138] Default exception handler: Het gevraagde bestand is niet gevonden Debug: \n* line 435 of /lib/setuplib.php: moodle_exception thrown\n* line 1568 of /lib/filelib.php: call to print_error()\n* line 3860 of /lib/filelib.php: call to send_file_not_found()\n* line 37 of /pluginfile.php: call to file_pluginfile()\n, referer: http://our.2.2.1.installation/mod/scorm/loadSCO.php?a=183&scoid=531&currentorg=WIE5_6755399441055843_nl_Content&attempt=1 When trying to add a new SCORM activity [Wed Mar 14 09:54:58 2012] [error] [client 83.163.190.138] Default exception handler: Foute inhoud pool-bestand 3213c0f4244e63cb1a1ce86e277d74da6160566c. Debug: \n* line 1163 of /lib/filestorage/file_storage.php: file_pool_content_exception thrown\n* line 959 of /lib/filestorage/file_storage.php: call to file_storage->add_string_to_pool()\n* line 353 of /lib/filestorage/zip_packer.php: call to file_storage->create_file_from_string()\n* line 217 of /lib/filestorage/stored_file.php: call to zip_packer->extract_to_storage()\n* line 229 of /mod/scorm/locallib.php: call to stored_file->extract_to_storage()\n* line 126 of /mod/scorm/lib.php: call to scorm_parse()\n* line 443 of /course/modedit.php: call to scorm_add_instance()\n, referer: http://our.2.2.1.installation/course/modedit.php?add=scorm&type=&course=199&section=1&return=0
          Hide
          Carlos Escobedo Orea added a comment -

          In our particular case (Moodle 2.2.1+ (Build: 20120202)) with a scorm file to resolve it we have broken the code in the file /lib/filestorage/filestorage.php in add_file_to_pool function in order to add the following line before throw new file_pool_content_exception($contenthash);

          echo $hashfile;
          die();
          throw new file_pool_content_exception($contenthash);

          So we can locate the file (which has 0bytes) in the moodledata/filedir/... and delete it. Is ugly solution but at least, we can continue working.

          Show
          Carlos Escobedo Orea added a comment - In our particular case (Moodle 2.2.1+ (Build: 20120202)) with a scorm file to resolve it we have broken the code in the file /lib/filestorage/filestorage.php in add_file_to_pool function in order to add the following line before throw new file_pool_content_exception($contenthash); echo $hashfile; die(); throw new file_pool_content_exception($contenthash); So we can locate the file (which has 0bytes) in the moodledata/filedir/... and delete it. Is ugly solution but at least, we can continue working.
          Hide
          Virgil Ashruf added a comment -

          Is there any progress on how to solve this on updated environments?

          Show
          Virgil Ashruf added a comment - Is there any progress on how to solve this on updated environments?
          Hide
          Charles Fulton added a comment -

          We encountered this after our production server temporarily ran out of disk space. File uploads would fail with various misleading messages (since behavior under those conditions is indeterminate), but second attempts would throw a file pool content exception. We found that despite the upload failing, a null file like Carlos described gets created in the filesystem, although there's no corresponding entry in the database. For us this was completely unrelated to SCORM, and it was on a clean 2.3.1 system.

          There are two ways to attack this. One would be figure out why these null files are getting created and correct that behavior. Another would be to add a check in add_file_to_pool() when checking if the file exists to see if the file's actually stored in the database. If it's not, it should probably just be deleted from the filesystem and the upload be treated as a new file.

          Show
          Charles Fulton added a comment - We encountered this after our production server temporarily ran out of disk space. File uploads would fail with various misleading messages (since behavior under those conditions is indeterminate), but second attempts would throw a file pool content exception. We found that despite the upload failing, a null file like Carlos described gets created in the filesystem, although there's no corresponding entry in the database. For us this was completely unrelated to SCORM, and it was on a clean 2.3.1 system. There are two ways to attack this. One would be figure out why these null files are getting created and correct that behavior. Another would be to add a check in add_file_to_pool() when checking if the file exists to see if the file's actually stored in the database. If it's not, it should probably just be deleted from the filesystem and the upload be treated as a new file.
          Hide
          Mike Churchward added a comment -

          We have now had this happen as well. In our cases, it happened when files were uploaded to a site that had run out of disk space. After the disk space was corrected, they could not upload the same files - instead getting the "Incorrect pool file content" error.
          We were able to work around it by removing the files that had zero bytes from the file system. Once removed, the were able to be uploaded again.
          In our case, the upload was via SCORM on a Moodle 2.2.2 site.

          I think the problem needs to be fixed in the file API when uploads are performed. If they cannot be completed successfully, it should not leave Moodle in a broken state.

          Show
          Mike Churchward added a comment - We have now had this happen as well. In our cases, it happened when files were uploaded to a site that had run out of disk space. After the disk space was corrected, they could not upload the same files - instead getting the "Incorrect pool file content" error. We were able to work around it by removing the files that had zero bytes from the file system. Once removed, the were able to be uploaded again. In our case, the upload was via SCORM on a Moodle 2.2.2 site. I think the problem needs to be fixed in the file API when uploads are performed. If they cannot be completed successfully, it should not leave Moodle in a broken state.
          Hide
          Eloy Lafuente (stronk7) added a comment -

          U P S T R E A M I Z E D !

          Many thanks, this is now available in all the repos (git & cvs).

          Closing, ciao

          Show
          Eloy Lafuente (stronk7) added a comment - U P S T R E A M I Z E D ! Many thanks, this is now available in all the repos (git & cvs). Closing, ciao
          Hide
          Eloy Lafuente (stronk7) added a comment -

          Doh,

          somehow this issue was closed incorrectly when processing all the integrated issues this week. (sort of most voted and current in integration filters mix). Apologies for the confusion, reseting to previous status!

          Ciao, Eloy

          Show
          Eloy Lafuente (stronk7) added a comment - Doh, somehow this issue was closed incorrectly when processing all the integrated issues this week. (sort of most voted and current in integration filters mix). Apologies for the confusion, reseting to previous status! Ciao, Eloy
          Hide
          Aaron Anderson added a comment -

          The affected branches in this issue indicate that Moodle 2.0 and Moodle 2.2 are stable. However, I just experienced this same issue in Moodle 2.2.5 (Build 20120910). When this issue as addressed, please do not overlook the occurrence of this issue in v2.2.5. Thanks!

          Show
          Aaron Anderson added a comment - The affected branches in this issue indicate that Moodle 2.0 and Moodle 2.2 are stable. However, I just experienced this same issue in Moodle 2.2.5 (Build 20120910). When this issue as addressed, please do not overlook the occurrence of this issue in v2.2.5. Thanks!
          Hide
          Niranjan added a comment -

          Hi I am also facing the same issue in Moodle2.4. I am not able to uploaded a scorm file.

          Show
          Niranjan added a comment - Hi I am also facing the same issue in Moodle2.4. I am not able to uploaded a scorm file.
          Hide
          Matteo Scaramuccia added a comment -

          MDL-36959 should address most of the strange issues related with file system, out of space included.

          Show
          Matteo Scaramuccia added a comment - MDL-36959 should address most of the strange issues related with file system, out of space included.
          Hide
          Niranjan added a comment -

          The issues that I faced is not with out of space. It is with the scorm name or etc.. It worked when I republish the scorm with different name.

          Show
          Niranjan added a comment - The issues that I faced is not with out of space. It is with the scorm name or etc.. It worked when I republish the scorm with different name.
          Hide
          Matteo Scaramuccia added a comment -

          @Niranjan: can you describe the exact steps to replicate the issue with a SCORM package, starting from the first step, upload, up to the step that unlock the publication? What chars in the filename? The more details the better, to help in finding one of the reasons for this "generic" issue.
          BTW, when you change the filename (at least 1 char in <filename>.zip) of the SCORM package, Moodle Files API will not get into conflicts with the previous package file: the short explanation is that for some reasons (e.g.: disk space, permissions, broken package) the file size of the file being uploaded and the one inside the Moodle file pool are different and changing the filename is a workaround more or less equal to find the offending entry in the pool and to delete it.

          Show
          Matteo Scaramuccia added a comment - @ Niranjan : can you describe the exact steps to replicate the issue with a SCORM package, starting from the first step, upload, up to the step that unlock the publication? What chars in the filename? The more details the better, to help in finding one of the reasons for this "generic" issue. BTW, when you change the filename (at least 1 char in <filename>.zip ) of the SCORM package, Moodle Files API will not get into conflicts with the previous package file: the short explanation is that for some reasons (e.g.: disk space, permissions, broken package) the file size of the file being uploaded and the one inside the Moodle file pool are different and changing the filename is a workaround more or less equal to find the offending entry in the pool and to delete it.
          Hide
          Matt Oquist added a comment - - edited

          This probably isn't a great fix, but it works, and I'm just hoping to get the conversation rolling on this again. We had our server drive fill up, and once we had cleared space, folks still couldn't upload the files they had tried earlier. This bug was why.

          Anyhow, here's a patch for 2.4.1+ (Build: 20130125).

          A better fix would verify that the file on disk has the checksum in the DB, and allow the user/admin to delete a file if it doesn't match. That's the more general case of what's happening here, when a file with no data has a checksum matching a file that DOES have data.

          Show
          Matt Oquist added a comment - - edited This probably isn't a great fix, but it works, and I'm just hoping to get the conversation rolling on this again. We had our server drive fill up, and once we had cleared space, folks still couldn't upload the files they had tried earlier. This bug was why. Anyhow, here's a patch for 2.4.1+ (Build: 20130125). A better fix would verify that the file on disk has the checksum in the DB, and allow the user/admin to delete a file if it doesn't match. That's the more general case of what's happening here, when a file with no data has a checksum matching a file that DOES have data.
          Hide
          Petr Škoda added a comment -

          This should be aleady fixed in 2.5 together with other potential filepool problems, please upgrade if possible.

          Show
          Petr Škoda added a comment - This should be aleady fixed in 2.5 together with other potential filepool problems, please upgrade if possible.
          Hide
          Petr Škoda added a comment -

          Closing as duplicate, MDL-36959 seems to have fixed these problems. Thanks for the report.

          Show
          Petr Škoda added a comment - Closing as duplicate, MDL-36959 seems to have fixed these problems. Thanks for the report.

            People

            • Votes:
              33 Vote for this issue
              Watchers:
              28 Start watching this issue

              Dates

              • Created:
                Updated:
                Resolved: