4

You get the error because your (non-root) shell tried to expand the glob /var/lib/docker/* and was unable (because /var/lib/docker isn't readable by your user). Your shell then left the glob intact, leaving a literal asterisk for sudo, which is what du is complaining about: du: cannot access '/var/lib/docker/*': No such file or directory ... because there ...


2

What I would do first is trying to identify what filled the drive. According to your mounts I would start checking /home, /usr or /var (/var keeps logs, maybe a process is generating too much error messages in your logs) disk usage, once you find a directory that took your space go down and find subdirs. Once you nailed it you can see if it was your problem ...


1

[root@host]# df -h /mydir Filesystem Size Used Avail Use% Mounted on /dev/mapper/myvg-mylv 10G 7.0G 3.1G 70% /mydir shows the file system size, not the LV size. The LV could easily be 20G in size (as reported by lvresize); this would happen for instance if someone resized the LV but ...


Only top voted, non community-wiki answers of a minimum length are eligible