Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

using NFS-mounted folder as data fails with 'not writable' #11145

Closed
dromer opened this issue Sep 10, 2018 · 7 comments
Closed

using NFS-mounted folder as data fails with 'not writable' #11145

dromer opened this issue Sep 10, 2018 · 7 comments
Labels
0. Needs triage Pending check for reproducibility or if it fits our roadmap bug feature: filesystem

Comments

@dromer
Copy link

dromer commented Sep 10, 2018

So I have mounted a legacy owncloud folder over nfs to this machine. Php is running a pool as the user 'nextcloud' and all files are owned by this user and the group permissions are for 'www-data' (as which the webserver is running). If I su nextcloud I can read/write everything on this share.

However when I browse to nextcloud I end up with the typical Your data directory is not writable and I have no idea why this is so.

Server configuration

Operating system: debian/yunohost
Web server: nginx
Database: mysql
PHP version: 7.0
Nextcloud version: 13.0.5

@nextcloud-bot
Copy link
Member

GitMate.io thinks possibly related issues are #9888 (Using local mounted NFS share with External storages does not work properly ), #8162 (External storage mount silently fails when http user has no rx access on folder), #7959 (Failed to remove sensitive data), #5471 (mount.cifs as data directory), and #9838 (Share folder failed on readonly storage).

@dromer
Copy link
Author

dromer commented Sep 10, 2018

I'm not using this as 'External storage'. It is mounted on the host machine and used directly as data folder.

@dromer
Copy link
Author

dromer commented Sep 11, 2018

So, according to folks in #php irc channel the is_writable() check is "known to return unusable results on file systems with less than trivial ACL setups." and for a proper check it should "actually try to open a file with write permissions".

So there you go. Hereby I propose that is_writable() is replaced with a function that actually tries to check write-permissions by writing a file.

@ChristophWurst
Copy link
Member

cc @icewind1991 :)

@stale
Copy link

stale bot commented Jun 6, 2019

This issue has been automatically marked as stale because it has not had recent activity and it seems to be missing some essential informations. It will be closed if no further activity occurs. Thank you for your contributions.

@stale stale bot added the stale Ticket or PR with no recent activity label Jun 6, 2019
@dromer
Copy link
Author

dromer commented Jun 7, 2019

If this is not marked as fixed then it is still an issue.

@stale stale bot removed the stale Ticket or PR with no recent activity label Jun 7, 2019
@kesselb
Copy link
Contributor

kesselb commented Jun 8, 2019

#13237

@kesselb kesselb closed this as completed Jun 8, 2019
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
0. Needs triage Pending check for reproducibility or if it fits our roadmap bug feature: filesystem
Projects
None yet
Development

No branches or pull requests

4 participants