Files seem to be saving to wrong storage device (LUKS)

I couldn't login to my web interface and upon further inspection I found out it was because my root drive is full.

I think this is because my files are being save to the wrong storage device even tough they are being saved to "/srv/dev-disk-by-label-OMV"

My drive is LUKS encrypted and I'm using the encryption plugin

Below is some bash output that should be useful

My file system: https://pastebin.com/Y2Qu486m

Filtered to min of 1G: https://pastebin.com/iizr7Rzm with deeper indexation

Output of:

pi@raspberrypi:/srv/dev-disk-by-label-OMV $ dpkg -l | grep openmediavault
ii  openmediavault                   5.5.17-3                            all          openmediavault - The open network attached storage solution
ii  openmediavault-downloader        5.1                                 all          OpenMediaVault downloader plugin
ii  openmediavault-flashmemory       5.0.7                               all          folder2ram plugin for OpenMediaVault
ii  openmediavault-keyring           1.0                                 all          GnuPG archive keys of the OpenMediaVault archive
ii  openmediavault-luksencryption    5.0.2                               all          OpenMediaVault LUKS encryption plugin
ii  openmediavault-lvm2              5.0.2-1                             all          openmediavault Logical Volume Manager (LVM2) plugin
ii  openmediavault-omvextrasorg      5.4.2                               all          OMV-Extras.org Package Repositories for OpenMediaVault


pi@raspberrypi:/srv/dev-disk-by-label-OMV $ lscpu
Architecture:        armv7l
Byte Order:          Little Endian
CPU(s):              4
On-line CPU(s) list: 0-3
Thread(s) per core:  1
Core(s) per socket:  4
Socket(s):           1
Vendor ID:           ARM
Model:               3
Model name:          Cortex-A72
Stepping:            r0p3
CPU max MHz:         1500.0000
CPU min MHz:         600.0000
BogoMIPS:            270.00
Flags:               half thumb fastmult vfp edsp neon vfpv3 tls vfpv4 idiva idivt vfpd32 lpae evtstrm crc32

Thank you all for taking a look

Thank you both for the replies

Quote from gderf

This problem usually involves two possibilities:

1) Some type of device is mounted to srv/dev-disk-by-label-OMV and the files are written to the mounted device.

2) There is no device mounted to srv/dev-disk-by-label-OMV and the files are written to the mountpoint directory, filling up the rootfs.

You need to be sure that some device is in fact mounted there before writing there.

Display More

This is indeed what I figured be the case sometimes I reboot the device and I have to remount the enrypted partition, but I have some docker containers(/auto backups) that really like writing files to the filesystem so they'll end up on the on the wrong device.

Quote from macom

If you use du with the -x option it will not evaluate directories in other file systems. So in case of 1) it should show very small size for /srv and in case of 2) it should show a very large size.

But it could be that this is not working, if the device was not mounted during copying and has been mounted since then.

Sadly the case seems to be the latter but it is good to know I assesed the problem right.

sudo du / -h --max-depth=1 -x

1.7M /srv

6.5G /var

4.0K /mnt

7.2M /etc

4.0K /export

1.7G /usr

482M /portainer

160K /home

16K /lost+found

4.0K /media

41M /opt

4.0K /sharedfolders

48K /root

8.6G /

Any clue how to create a bash script to copy all the files to the right device with the same path?

My search engine skills as of the moment don't seem to be able to locate me a way to check if a file exists on the root file system or another one.

I figure attaching another external storage device and rsyncing then deleting and syncing back should do it but i'd obviously preffer a solution that i could setup as a cron job and just run once a month.

As i'm planning to deploy one of these at my mothers house to have off site backups.

For now i fixed it by moving all my files to another hdd and then moving them back, leaving this here for the search engine surfers

rsync -r /srv/full-device-name /mnt/media/
rm -rf /srv/full-device-name
rsync -r /mnt/media /srv/full-device-name

If anyone has a more permanent solution please let me know as this is bound to happen again, and this is far for ideal