Score:0

Cannot determine what is taking up space on Ubuntu lv

in flag

As you can see here my root volume on / shows full via df -h.

Filesystem                         Size  Used Avail Use% Mounted on
udev                                16G     0   16G   0% /dev
tmpfs                              3.2G  1.6M  3.2G   1% /run
/dev/mapper/ubuntu--vg-ubuntu--lv  196G  185G 1009M 100% /
tmpfs                               16G     0   16G   0% /dev/shm
tmpfs                              5.0M  4.0K  5.0M   1% /run/lock
tmpfs                               16G     0   16G   0% /sys/fs/cgroup
/dev/nvme0n1p2                     976M  300M  609M  34% /boot
/dev/nvme0n1p1                     511M  5.3M  506M   2% /boot/efi
/dev/loop0                          56M   56M     0 100% /snap/core18/2066
/dev/loop1                          56M   56M     0 100% /snap/core18/2074
/dev/loop2                          33M   33M     0 100% /snap/snapd/12704
/dev/loop3                          71M   71M     0 100% /snap/lxd/21029
/dev/loop5                          33M   33M     0 100% /snap/snapd/12398
/dev/loop4                          68M   68M     0 100% /snap/lxd/20326
192.168.1.10:/volume1/metrics       22T  5.5T   17T  26% /metrics
192.168.1.10:/volume1/media         22T  5.5T   17T  26% /data
tmpfs                              3.2G     0  3.2G   0% /run/user/1000

When I look at the contents of the directories via ncdu I see the following.

    5.3 TiB [##########] /data
   11.3 GiB [          ] /var
    8.0 GiB [          ]  swap.img
    5.9 GiB [          ] /home
    2.9 GiB [          ] /usr
    1.0 GiB [          ] /snap
  732.1 MiB [          ] /metrics
  302.6 MiB [          ] /boot
    5.3 MiB [          ] /etc
    1.5 MiB [          ] /run
   76.0 KiB [          ] /root
   60.0 KiB [          ] /tmp
   16.0 KiB [          ] /opt
e  16.0 KiB [          ] /lost+found
e   4.0 KiB [          ] /srv
e   4.0 KiB [          ] /mnt
e   4.0 KiB [          ] /media
e   4.0 KiB [          ] /cdrom
.   0.0   B [          ] /proc
    0.0   B [          ] /sys
    0.0   B [          ] /dev
@   0.0   B [          ]  libx32
@   0.0   B [          ]  lib64
@   0.0   B [          ]  lib32
@   0.0   B [          ]  sbin
@   0.0   B [          ]  lib
@   0.0   B [          ]  bin

We can ignore /data, it's just storage mounted via NFS. But the rest of the storage that's shown is roughly ~30GB. Not 185 as reported by du.

I've rebooted and done a full shutdown to purge any transient logs.

The output of sudo lsof +L1 shows the following:

COMMAND PID USER  FD   TYPE DEVICE SIZE/OFF NLINK  NODE NAME
none    877 root txt    REG    0,1    17032     0 32951 / (deleted)

I'm not sure what else or where else to look beyond this. I can expand the logical volume but I don't think that's the solution here.

in flag
Answered via @OldTroll here https://serverfault.com/questions/275206/disk-full-du-tells-different-how-to-further-investigate I unmounted my /data mount and found that some things had accumulated there once when my NAS failed to mount.
mangohost

Post an answer

Most people don’t grasp that asking a lot of questions unlocks learning and improves interpersonal bonding. In Alison’s studies, for example, though people could accurately recall how many questions had been asked in their conversations, they didn’t intuit the link between questions and liking. Across four studies, in which participants were engaged in conversations themselves or read transcripts of others’ conversations, people tended not to realize that question asking would influence—or had influenced—the level of amity between the conversationalists.