Nextcloud database on system SSD

Hi guys,

in my case, OMV is installed on a 120GB SSD and I have 2 HDDs for data storage. I installed the Nextcloud-Docker (linuxserver) broadly similar to the guides by TechnoDadLife and macom . In both cases, the three folders needed (config for database and nextcloud, data) are created on the data drives. I'm wondering if it is possible to move (or set) the two config folders, i.e. the database and appdata of nextcloud, to my system SSD, especially regarding permissions. Would there be noticeable advantages?

This question is basically not limited to Nextcloud, as I want to run e.g. my Digikam-database on my server as well.

Many thanks for your help

Zitat von auanasgheps

Absolutely yes!

All my docker apps run from my SSD, and in general it's a good idea. Nextcloud is quite "big" and will definitely get some boost.

Does your SSD have only one partition used by OMV? If yes, you'll have to repartition the drive (use gParted), create a new file system and use it for docker apps.

I haven't thought about repartitioning, thank you!

Zitat von auanasgheps

Absolutely yes!

All my docker apps run from my SSD, and in general it's a good idea. Nextcloud is quite "big" and will definitely get some boost.

Does your SSD have only one partition used by OMV? If yes, you'll have to repartition the drive (use gParted), create a new file system and use it for docker apps.

Further question: Did you put only your "files" folders on your HDDs or the whole /data-Volume including e.g. "appdata_..." or "ownbackup"?

I'm currently trying to link the "files"-folders to the user home directories using the Symlink-plugin, but I can't quite get it working. When I'm linking a "files" folder from inside the /data-Volume to a home directory I cannot open it with that user, some permissions are wrong here. When I do it vice-versa, i.e. moving the "files" folder to the home directory and linking it to the /data-Volume the symlink doesn't even show up. I've set ACL of this folder to rwe for all users. My goal is, that every user can access their Nextcloud files, but only theirs, through SMB or NFS as well.

Edit: Apparently Nextcloud creates the folders inside the /data-Volume read-only for the users group, only the owner I set with PUID has write access. So I gave my user rw-access to his nextcloud folder and subfolders on the /data-Volume through ACL. Now I can write when accessing the /data-Volume directly via SMB, but I'm still getting this network access error saying I don't have permissions when trying to open this folder with the symlink in my home folder

I was able to get it working in the meanwhile, setting wide links = yes and unix extensions = no in the smb.conf fixed it. Thus the symlink in the users home directory to his nextcloud folder works now as expected

Zitat von auanasgheps

I'm not sure if I understood your question, but:

on my SSD, I have the following shared folders:

• docker-install: where docker binaries are stored. It's not shared with anyone, you don't want to mess with those files
• docker-apps: where my container's data are stored. I created a folder for each container to store its data.

This allows my docker ecosystem to run independently by HDDs (I want them to spindown).

The Nextcloud-container creates two volumes (at least on my system, I still have related stuff in /var/lib/docker though, I believe): /data and /config. In the /data volume there's one folder for every user with 'cache' and 'files' subfolders respectively and folders called 'appdata_...', 'files_external' and 'ownbackup' and some files. I don't know how big this stuff may grow, except for 'files', or if moving them to my SSD would affect speed in some way, thus my question if you got your /data volume on your HDDs as a whole, or only the 'files' folders. I guess the /config volumes of your nextcloud and database are in docker-apps in your case?

Zitat von auanasgheps

Most of /data should be filled with data created by users who are not using your external storage. I don't care about /data, but I still placed on the SSD for good folder placement.

Ahh, now I get it as well. I didn't know it's possible to mount an external storage in NC, I'll have a look at this

Zitat von auanasgheps

I thought you were trying to do that! Probably is the only "right" way of accessing existing data with Nextcloud.

Of course, but I didn't know it was possible from within Nextcloud.

In the meanwhile, another issue arrose. How did you manage to mount your HDDs in nextcloud? It looks that this is only possible for folders inside /media on the same partition where nextcloud is installed. I'm constantly getting 'stat(): stat failed' error, no matter which permissions I set.

Zitat von macom

In Nextcloud there is an "external storage support" app. With that you are able to access for example any SMB/CIFS share.

Indeed, that's what I was writing about. But mounting them locally doesn't seem to work.

Zitat von macom

Works for me.

Maybe we're talking about different things. Mounting your external folders via 'local' works for you?

I'm getting the same stat error when mounting with samba btw.

Zitat von Morlan

To mount a local external storage you need to bind mount the folder via the -v flag in your container settings

Ahh, great. Thank you! This is so much easier, then I don't have to mess around with privileges and permissions that don't do what I'm expecting.

Looks like everything is working now, thank you all!