Upgraded to 10.1--extra file integrity scan question

I have just upgraded from 10.0.10 to 10.1 via centos package manager. Everything as usual except on service restart. There is an extra file

Technical information

The following list covers which files have failed the integrity check. Please read
the previous linked documentation to learn more about the errors and how to fix


  • core
      • INFO

Raw output

[core] => Array
[EXTRA_FILE] => Array
[INFO] => Array
[expected] =>
[current] => cf83e1357eefb8bdf1542850d66d8007d620e4050b5715dc83f4a921d36ce9ce47d0d13c5d85f2b0ff8318d2877eec2f63b931bd47417a81a538327af927da3e




This is coming from the 0 byte README.markdown in /lib/composer/doctrin/dbal/lib/Doctrine/DBAL/README.markdown

deleting the file causes other files to become failures upon integrity re-scan. Is this just a bug or will this affect my owncloud?

I also downloaded the source in zip format and the README.markdown file is 0 bytes in that as well. Thanks for the help!

EDIT: There appear to be multiple files with this signature. cf83e1357eefb8bdf1542850d66d8007d620e4050b5715dc83f4a921d36ce9ce47d0d13c5d85f2b0ff8318d2877eec2f63b931bd47417a81a538327af927da3e

–so it may not be the README.markdown file.


You have a <whereverOCis>/core/INFO file, which isn’t part of the installation. Either remove it or move it out of the ownCloud installation.

1 Like


What is the quickest way to find it?

EDIT: It was not located in <whereverOCis>/core/
There was an INFO file in main install dir of OC. Removing that fixed problem. Thanks!

1 Like