urbackup filled system disk

  • Hello!

    After a power outage urbackup used system disk instead of the previously configured disk for backing up files. Now I would like to delete the urbackup files on the system disk, but I can't find the correct location.


    I can't login to omv because of system disk usage 100%, urbackup admin is stuck on "urbackup is upgrading its internal database". Rebooting omv and restarting urbackup docker container does not help.


    So my question is where are the backups located on the system disk?

  • It seems like you are using the urbackup docker. So it should save the files on the location which you specified when setting up the docker. If it was on a external disk, which is not available anymore it might have created a folder under the file path in /srv/dev-disk-by-label-...

    Or if you did not change the docker base path it might be in /var/lib/docker

  • This might help you figure out where to look:


    https://www.cyberciti.biz/faq/…ecursively-using-find-du/



    /dev/disk/by-id/ata-KINGSTON_SA400S37120G_50026B76834417D9-part1.


    /srv/dev-disk-by-label-...

    Check the path again. /srv/ not /dev


    Greetings

    David

    "Well... lately this forum has become support for everything except omv" [...] "And is like someone is banning Google from their browsers"


    Only two things are infinite, the universe and human stupidity, and I'm not sure about the former.

    Upload Logfile via WebGUI/CLI
    #openmediavault on freenode IRC | German & English | GMT+1
    Absolutely no Support via PM!

  • Thanks davidh2k for the link!


    This is what I get when i df /srv/.

    /dev/sdg1 is the system disk. When I cd or df /dev/sdg1 I get Not a directory.



    I also ran a

    Code
    du -a / | sort -n -r | head -n 20

    from root. It checked all other locations BUT the system disk. Is this because of the "no need to have access to system disk" nature of omv?


    There is some critical info missing in my understanding about this os, and it bugs me to pieces :D

  • What is the full path to the location of where the backups are supposed to be written?

    --
    Google is your friend and Bob's your uncle!


    OMV AMD64 7.x on headless Chenbro NR12000 1U 1x 8m Quad Core E3-1220 3.1GHz 32GB ECC RAM.

  • What is the full path to the location of where the backups are supposed to be written?

    This is the correct place

    /srv/dev-disk-by-id-ata-WDC_WD20EFRX-68EUZN0_WD-WCC4M3ZD1HSR-part1/backups


    After a power outage urbackup filled up the system disk instead of the correct path. I can't find the location on the system disk though. Or more likely, I don't know how to access the system disk.

  • Code
    cd $(mount | grep sdg1 | cut -d' ' -f3);
    find . -type f -size +100M; # Files > than 100 Megabytes, use G for Gigs
    
    
    cd /srv/dev-disk-by-id-ata-WDC_WD20EFRX-68EUZN0_WD-WCC4M3ZD1HSR-part1/backups;
    rm (whatever)

    NOTE: It is extremely hard to find a tutorial for UNIX that both starts with something like 'cd' and is short and concise. I just spent 5 minutes looking for one and all I found were things right above the level of 'cd' (like variables) or they were EXTREMELY long winded (one was 10 pages for 3 commands!)

    Edited 4 times, last by olduser ().

  • In a root shell run:


    Code
    umount --force /srv/dev-disk-by-id-ata-WDC_WD20EFRX-68EUZN0_WD-WCC4M3ZD1HSR-part1

    Then run:


    Code
    ls -al /srv/dev-disk-by-id-ata-WDC_WD20EFRX-68EUZN0_WD-WCC4M3ZD1HSR-part1

    Anything of interest in there?

    --
    Google is your friend and Bob's your uncle!


    OMV AMD64 7.x on headless Chenbro NR12000 1U 1x 8m Quad Core E3-1220 3.1GHz 32GB ECC RAM.

  • In a root shell run:


    Code
    umount --force /srv/dev-disk-by-id-ata-WDC_WD20EFRX-68EUZN0_WD-WCC4M3ZD1HSR-part1

    Then run:


    Code
    ls -al /srv/dev-disk-by-id-ata-WDC_WD20EFRX-68EUZN0_WD-WCC4M3ZD1HSR-part1

    Anything of interest in there?

    Yes! but I ran it on /dev/disk/by-id/ata-KINGSTON_SA400S37120G_50026B76834417D9-part1 wich is the system disk that needs to be cleaned up

    Result:

    Code
    lrwxrwxrwx 1 root root 10 Aug 26 21:47 /dev/disk/by-id/ata-KINGSTON_SA400S37120G_50026B76834417D9-part1 -> ../../sdg1



    Code
    WDC_WD20EFRX-68EUZN0_WD-WCC4M3ZD1HSR-part1

    is the correct disk for the backups:


    drwxrwxrwx 4 root root 4096 Feb 14 2019 .

    drwxr-xr-x 11 root root 4096 Mar 11 21:09 ..

    drwxr-xr-x 4 docker users 4096 Aug 25 08:55 backups

    drwxr-xr-x 3 root root 4096 Feb 14 2019 nexus

  • Code
    cd $(mount | grep sdg1 | cut -d' ' -f3);
    find . -type f -size +100M; # Files > than 100 Megabytes, use G for Gigs
    
    
    cd /srv/dev-disk-by-id-ata-WDC_WD20EFRX-68EUZN0_WD-WCC4M3ZD1HSR-part1/backups;
    rm (whatever)

    NOTE: It is extremely hard to find a tutorial for UNIX that both starts with something like 'cd' and is short and concise. I just spent 5 minutes looking for one and all I found were things right above the level of 'cd' (like variables) or they were EXTREMELY long winded (one was 10 pages for 3 commands!)

    I'm looking at that, trying to modify it for directories. The files I'm looking for or mostly photos, but also som high def videos.

    I got

    Code
    bash: cd: too many arguments

    but got it to pass by removing a single quote. Still looking in to this too. And cleaning up after dinner :S

  • /dev/sdg1 is the system disk. When I cd or df /dev/sdg1 I get Not a directory.

    /dev is the device aka your hard disk, that is used to mount it to a path like /srv/... You can't access it directly.


    Yes! but I ran it on /dev/disk/by-id/ata-KINGSTON_SA400S37120G_50026B76834417D9-part1 wich is the system disk that needs to be cleaned up

    Result:


    That is wrong. Do it like gderf suggested. You constantly mix the device with the actual mounted path.


    You second HDD is mounted under the path you wrote, if this ceasis to exist, the backup still writes to the same path, just that that path is now on your OS disk. But that doesn't change the path.



    Greetings

    David

    "Well... lately this forum has become support for everything except omv" [...] "And is like someone is banning Google from their browsers"


    Only two things are infinite, the universe and human stupidity, and I'm not sure about the former.

    Upload Logfile via WebGUI/CLI
    #openmediavault on freenode IRC | German & English | GMT+1
    Absolutely no Support via PM!

  • THANK YOU! This makes things a bit clearer.

  • Ok, so here's how i finally solved it: I took out the disk and mounted it in my dual boot win10/Ubuntu machine.



    And when I saw the file system this way, detached from omv, I finally understood what gderf and davidh2k meant about same paths regardless disk. Thanks once again, 89,2 GB of free space recovered!

Participate now!

Don’t have an account yet? Register yourself now and be a part of our community!