Uploaded image for project: 'Moodle'
  1. Moodle
  2. MDL-36959

file_pool_content_exception is ambiguous under some circumstances

XMLWordPrintable

    • Icon: Improvement Improvement
    • Resolution: Fixed
    • Icon: Minor Minor
    • 2.5
    • 2.4, 2.5
    • Files API
    • MOODLE_24_STABLE, MOODLE_25_STABLE
    • MOODLE_25_STABLE
    • w16_MDL-36959_m25_poolhashes
    • Hide

      A/ execute phpunit tests

      B/ optionally try to simulate following problems which should be now detected:

      • read only filepool (this is similar to full disk) - expected exception
      • incorrect pool file content (you need to make the pool file bigger or smaller) - the changed pool file should be automatically fixed if you upload it again
      Show
      A/ execute phpunit tests B/ optionally try to simulate following problems which should be now detected: read only filepool (this is similar to full disk) - expected exception incorrect pool file content (you need to make the pool file bigger or smaller) - the changed pool file should be automatically fixed if you upload it again

      There are several posts telling about this exception, some of them related to the SCORM activity: most of the times the solution is to look at the pool, both filedir/ and DB table, to find out that a file with the same hash exists but with different size (most of the time, 0).

      Since the new file system is sensible to both file permissions and disk space (and maybe to "hidden" issues in some modules like SCORM), it could be helpful to differentiate the exceptions in adding a file to the pool to let the system be more accurate in telling what's going on.

            skodak Petr Skoda
            matteo Matteo Scaramuccia
            Aparup Banerjee Aparup Banerjee
            Damyon Wiese Damyon Wiese
            Rajesh Taneja Rajesh Taneja
            Votes:
            2 Vote for this issue
            Watchers:
            6 Start watching this issue

              Created:
              Updated:
              Resolved:

                Error rendering 'clockify-timesheets-time-tracking-reports:timer-sidebar'. Please contact your Jira administrators.