Run a df -h and see if perhaps the disk was partitioned incorrectly. You’ll see there is an “avail” column and you can match it up accordingly with the drive/partition your nexctloud storage is on
Can’t argue with that since I was going to do exactly that, but I thought perhaps given the Nextbox is a standardized machine I might get other suggestions.
Pulling up that information does reveal the problem, but I don’t know what to do about it. It appears there’s something taking up a whole lot of space on sda2, much more that I actually have stored in Nextcloud.
I’m not sure what you mean by which filesystem am I using. This is the setup as created by using the Nextcloud Box image on the SD card that came with it. Whatever that is, that’s it.
Is there a command line command or combination of commands that would tell the answer to that question?
In general, I would expect all the workings required by the Nextcloud software would be on /dev/sda2. Those /dev/loop# lines appear to be created by each update?
I understand that such questions would be necessary if I were running Nextcloud on some unspecified setup, but in this case I received the Nextcloud Box, set it up as instructed with the SD card that came with it, and that’s the extent of the setup. I haven’t made any special changes to the environment.
In the meantime, I’m going to try some commands I am unfamiliar with to get some details on what is using all that space. Variations on the “du” command I believe.
df -T
should list the filesystems. I have no special experience with the nextcloud box just the idea that it might be some snapshots that are using up the space.
I attempted to get more information that might be useful. Where was all this stuff taking up far more space than expected. A series of “du” commands got me down to the level of /var/snap/nextcloud/common/nextcloud
I can’t “cd” into nextcloud at the level because “Permission denied”. Since sudo doesn’t work, I’m not sure how I get past that.
There seemed to be more in the trash than I expected. I didn’t see a total size indicator, but I’ll see what the result of selecting everything and deleting it is.
I’ve been waiting many minutes for the spinning circle to stop spinning. Either something is stuck, or it takes a lot of work to get rid of whatever was in the trash bin.
The size of the files in the trash bin seems to have been the issue. df -h indicates the used space is down to 243GB after I deleted everything in there, which is probably about right.
If there was some screen in the web interface for Nextcloud that could have told me about this situation, and I did look right off, I didn’t find it.
For the future try to set a trashbin retention policy in nextcloud/config/config.php
like described here:
since cd is not a program in the classical sence, you cant sudo it. Try
sudo su -
to switch to the root user. Be careful. Working as root is not recommended, but preferable to weakening permissions on the data folder. Only use that if you know exactly what you are doing.
Indeed, I remembered that sudo su business while driving home. Forget what I used it for last time, and I believe I just tried it to get some job done and was amazed that it worked.
Might even have been for one of my previous own/Nextcloud installs.
I was puzzled that there was no retention policy setting I could find in the admin screens. Good to know there is such a thing you can get to if you need it.
You should take a look at config.sample.php (same folder as config.php)
There are a ton of useful config settings in there with explaination, which are not available via th WebGui