[NC 18.0] Disk ran full, but it is the wrong device

ℹ️ Support
1

Nextcloud version (17):
Operating system and version Ubuntu 18
Apache or nginx version not sure_:
PHP version 7.1)

My disk seems full, nextcloud hangs

Steps to replicate it:

Output of df -h:

``
Filesystem Size Used Avail Use% Mounted on
udev 16G 0 16G 0% /dev
tmpfs 3.2G 1.1M 3.2G 1% /run
/dev/sda2 251G 239G 127M 100% /
tmpfs 16G 0 16G 0% /dev/shm
tmpfs 5.0M 0 5.0M 0% /run/lock
tmpfs 16G 0 16G 0% /sys/fs/cgroup
/dev/loop3 92M 92M 0 100% /snap/core/8689
/dev/loop1 218M 218M 0 100% /snap/nextcloud/19299
/dev/loop0 94M 94M 0 100% /snap/core/8935
/dev/loop2 219M 219M 0 100% /snap/nextcloud/20007
tmpfs 3.2G 0 3.2G 0% /run/user/0


Output of sudo lsblk -o NAME,FSTYPE,SIZE,MOUNTPOINT,LABEL

NAME FSTYPE SIZE MOUNTPOINT LABEL
loop0 squashfs 93.8M /snap/core/8935
loop1 squashfs 217.6M /snap/nextcloud/19299
loop2 squashfs 218.4M /snap/nextcloud/20007
loop3 squashfs 91.4M /snap/core/8689
sda 58.6T
├─sda1 1M
└─sda2 ext4 256G /
sr0 1024M


All user data seems to be on sda2 ext4 should be on sad 58.6T

What is wrong?
2

You appear to have a 251 GB partition that’s full. Can you post output of:

fdisk -l /dev/sda
3

GPT PMBR size mismatch (536870911 != 125829119999) will be corrected by w(rite).
Disk /dev/sda: 58.6 TiB, 64424509440000 bytes, 125829120000 sectors
Units: sectors of 1 * 512 = 512 bytes
Sector size (logical/physical): 512 bytes / 512 bytes
I/O size (minimum/optimal): 512 bytes / 512 bytes
Disklabel type: gpt
Disk identifier: 8E59B0B4-69F3-4574-A014-280C16E86391

Device Start End Sectors Size Type
/dev/sda1 2048 4095 2048 1M BIOS boot
/dev/sda2 4096 536868863 536864768 256G Linux filesystem

4

Stange that you have a 58.6 TiB disk and only use 256GiB

Can you output sudo smartctl -i /dev/sda

5

Running a VM Ware disk consolidation, before that finishes I have no access to CLI of the Nextcloud VM

6

The fdisk output confirms it. Your root partition is only 256 GB, and it’s full. That sounds more like an issue with how your OS was set up, rather than something actually being wrong.

You should be able to extend the root partition in place since the remainder of the free space is contiguous following it. You can find various guides online for different methods to do this. I’m not going to vouch for a particular one without knowing more about your system.

Now, if I could offer a little bit of advice. I don’t know how deep you are into using this system yet, but I would have installed it with LVM. Although it does add some steps to something like a partition resize, it also opens up a lot of options for how to approach this kind of situation, some of which are much safer than what you’re about to have to do. Definitely take a snapshot before resizing.

Another thing to consider. You may want a separate virtual disk to house NC’s data folder. If your database is on the root partition, and that partition is unable to write due to filling up, it can lead to problems with the database, not to mention other various parts of the OS.

7

I don t know exactly, i once made a snap in VM, today I first had to consolidate this snap. Than deleted all Snapshots. In the VMware interface the disk provisioning now shows a disk size of 59Tb. Before I could not change that disk size. fdisk -l /dev/sda now shows

Device Start End Sectors Size Type
/dev/sda1 2048 4095 2048 1M BIOS boot
/dev/sda2 4096 536868863 536864768 256G Linux filesystem

So it seems as if nothing changed,

8

Nothing you do in VMware will change the partitioning of the disk. This has to be done in the VM.

9

=== START OF INFORMATION SECTION ===
Vendor: VMware
Product: Virtual disk
Revision: 1.0
User Capacity: 64,424,509,440,000 bytes [64.4 TB]
Logical block size: 512 bytes
LU is fully provisioned
Device type: disk
Local Time is: Sat Apr 18 12:33:11 2020 UTC
SMART support is: Unavailable - device lacks SMART capability.