NextCloud Not Using All Available SSD Space

ℹ️ Support
1

Hey Guys. Very new to NextCloud/Docker/Linux… everything.

I’ve got my NextCloud up and running and everything works great. I can access remotely from other PCs and smart phones. Everything seems to be great. The only problem I am having is that my NextCloud says there’s only 15GB available, but I’ve got a 2TB NvME that the server is running on. I’m not sure how to get the rest of the space available for use in my environment.

df -h shows:

df -h
Filesystem      Size  Used Avail Use% Mounted on
overlay        1007G  4.6G  952G   1% /
tmpfs            64M     0   64M   0% /dev
tmpfs            16G     0   16G   0% /sys/fs/cgroup
shm              64M     0   64M   0% /dev/shm
/dev/sdd       1007G  4.6G  952G   1% /etc/hosts
overlay          16G  2.5G   14G  16% /var/www/html
tmpfs            16G     0   16G   0% /proc/acpi
tmpfs            16G     0   16G   0% /sys/firmware

I used portainer to deploy and the script that I used said to store data in /var/www/html which appears to be why it’s not showing the entire SSD… but that said, none of the items in that list show the full 2TB SSD. I only have 1 storage device in the server currently. Any assistance would be greatly appreciated!

Thanks!

2

Does anyone have any ideas on this? I’m really hoping I don’t have to start over. But even if I did start over, I’m not sure where I went wrong and the data folder went on the smaller partition so I wouldn’t know how to avoid it happening again.

3

Please share your Docker compose.

However, it sounds like the issue is this: the Docker Engine stores all named volumes in /var/lib/docker/volumes on the underlying host. There are numerous ways to tackle your situation, but if the large drive (or a partition on it) can be dedicated to storing your Docker volumes you can simply mount that partition as /var/lib/docker/volumes.

You will need to migrate your existing data on the underlying host that already exists in /var/lib/docker/volumes to the new drive/partition. All of this happens outside of Nextcloud. It’s an OS level issue.

4

@jtr Thank you so much for replying. Like I said, I’m very new to all of this so it’s a bit confusing. My Docker compose is below:

version: “2”
services:
app:
depends_on:
- db
environment:
- MYSQL_PASSWORD=
- MYSQL_DATABASE=nextcloud
- MYSQL_USER=nextcloud
- MYSQL_HOST=db
image: nextcloud
links:
- db
ports:
- “8080:80”
restart: always
volumes:
- “/path/to/nextcloud:/var/www/html”
- “/path/to/apps:/var/www/html/custom_apps”
- “/path/to/config:/var/www/html/config”
- “/path/to/data:/var/www/html/data”
- “/path/to/theme:/var/www/html/themes/<YOUR_CUSTOM_THEME>”
db:
command: “–transaction-isolation=READ-COMMITTED --binlog-format=ROW”
environment:
- MYSQL_ROOT_PASSWORD=
- MYSQL_PASSWORD=
- MYSQL_DATABASE=nextcloud
- MYSQL_USER=nextcloud
image: “mariadb:10.5”
restart: always
volumes:
- “/path/to/db:/var/lib/mysql”

5

Any advice/ideas/help?