Integrity check stumbles over lost+found special directory #23341

Closed
stephan2012 opened this Issue Mar 17, 2016 · 4 comments

Projects

None yet

5 participants

@stephan2012

Dear owncloud maintainers,

my ownCloud 9.0 installation lives on a dedicated ext4 filesystem mounted on /var/www/owncloud. As usual it has a lost+found directory granting access to root only. ownCloud runs as a different user and has no access to it. Thats why the new integrity check throws an exception on it:

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
them.

Results
=======
- core
    - EXCEPTION
        - UnexpectedValueException
        - RecursiveDirectoryIterator::__construct(/var/www/owncloud/lost+found): failed to open dir: Permission denied

Raw output
==========
Array
(
    [core] => Array
        (
            [EXCEPTION] => Array
                (
                    [class] => UnexpectedValueException
                    [message] => RecursiveDirectoryIterator::__construct(/var/www/owncloud/lost+found): failed to open dir: Permission denied
                )

        )

)

It would be nice if ownCloud just skips the lost+found special directory on it's integrity check.

Server configuration

Operating system: Debian GNU/Linux 8.3

Web server: Nginx 1.9.10

Database: MySQL 5.6.27

PHP version: 5.6.17

ownCloud version: ownCloud 9.0.0 (stable)

Updated from an older ownCloud or fresh install: Update

Where did you install ownCloud from: Official Debian packages

@PVince81
Collaborator
@PVince81 PVince81 added this to the 9.0.2-next-maintenance milestone Mar 17, 2016
@nomeata
nomeata commented Mar 18, 2016

I can confirm this issue on my installation.

@LukasReschke LukasReschke self-assigned this Mar 18, 2016
@ghost
ghost commented Mar 19, 2016

Should be easy to fix: #23409

@stephan2012 @nomeata Can you test this and confirm at the PR if it is working for you?

@stephan2012

Works. Thank you. :-)

@LukasReschke LukasReschke removed their assignment Mar 22, 2016
@LukasReschke LukasReschke self-assigned this Mar 22, 2016
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment