Issue Bug Closed

#33622Filebackend reports error when trying to rename file due to concurrent processes

Peter Russ 02/02/12, 14:30 updated 01/08/25, 11:31

Description

Due to concurrent processes it happens that a temp-cache-file gets renamed while an other process is just writing it.
Further there is an error in the error handling.

We fixed both.
  1. added an exclusive lock for the writing operation
  2. added counters for a break to avoid an endless loop due to file system errors
  3. added timers for getting the process to sleep
  4. fixed error handling

As this is the same in FLOW3 I also reported the bug and fixes there.
see http://forge.typo3.org/issues/33621

Please find TYPO3 specific fixes attached.

Reviews 0

No change resolves or names this issue in its commit message, and no comment links one.

Files 1

History 12

  1. Peter Russ changed attached 33622.patch target version done 0 % 80 % <span data-processor="relativetime" data-value="2012-02-02T14:31:33+00:00" > 02/02/12, 14:31 </span>

  2. Marc Bastian Heinrichs commented <span data-processor="relativetime" data-value="2013-01-31T18:29:53+00:00" > 01/31/13, 18:29 </span>

    Exception timestamp is 1222361632, right?. Had this already on different systems, too.

    Peter, you uploaded the wrong patchfile, aren’t you?

  3. Max Roesch commented <span data-processor="relativetime" data-value="2013-03-11T16:58:16+00:00" > 03/11/13, 16:58 </span>

    Just stumpling upon this on a TYPO3 6.0.4 installation at Hosteurope.

    Core has the patch from FLOW3 but nevertheless I am running in the same error.

  4. Oliver Hader commented <span data-processor="relativetime" data-value="2013-04-14T12:45:13+00:00" > 04/14/13, 12:45 </span>

    The cache file “…/t3lib_l10n/3e2cbbda0301cf592e5831ef26c56b7b” could not be written.
    This issue has been solved on concurrent editing actions in the backend for 4.7, 6.0 and 6.1 in issue #46205
    However, that does not solve the original issue in the FileBackend that probably needs to be solved by locking mechanisms

  5. Andreas Kienast commented <span data-processor="relativetime" data-value="2024-12-20T14:04:23+00:00" > 12/20/24, 14:04 </span>

    This probably sounds like #91768, which has been tackled in the meantime. Therefore I’ll close this issue.