[Date Prev][Date Next] [Thread Prev][Thread Next] [Date Index] [Thread Index]

Re: [SOLVED] /root is full



I knew because you said that you had tried to backup some files to storage and
sdb13 was not mounted on storage. So where those files went was into /
partition. When you mounted sdb13 on top of /storage, all those files became
inaccessible but they were still there taking up stace. This happened to me 25 years ago (SunOS).

William G. Unruh   |  Canadian Institute for|     Tel: +1(604)822-3273
Physics&Astronomy  |     Advanced Research  |     Fax: +1(604)822-5324
UBC, Vancouver,BC  |   Program in Cosmology |     unruh@physics.ubc.ca
Canada V6T 1Z1     |      and Gravity       |  www.theory.physics.ubc.ca/

On Tue, 29 Jul 2014, Haines Brown wrote:

  # df
  Filesystem             1K-blocks     Used Available Use% Mounted on
  rootfs                    474440   474440         0 100% /
  udev                       10240        0     10240   0% /dev
  tmpfs                     830924     1572    829352   1% /run
  /dev/disk/by-uuid/d3a2... 474440   474440         0 100% /
  /dev/sdb5               48062440 10165348  35455616  23% /home
  /dev/sdb6               28834716  4261020  23108972  16% /usr
  /dev/sdb7               38448276  2372784  34122392   7% /var
  /dev/sdb8               19228276   994260  17257268   6% /tmp
  /dev/sdb9               38448276 12808004  23687172  36% /usr/local
  /dev/sdb12              96124904 11577356  79664596  13% /info
  /dev/sdb13             192243928 58177436 124300984  32% /storage

Note that find will NOT find files hidden under the mount point
/storage. And that is where the problem lies. You MUST unmount /storage
first to find those files.

William, you found the problem. I didn't think to look into /storage
mount point because the partition that was full was /, and so only
looked for unwanted files in /mnt and /media. How did you know that
/storage was the culprit, and how could it affect /?

I now have:

 $ df
 Filesystem                    1K-blocks     Used Available Use% Mounted on
 rootfs                           474440   257750    192193  58% /
 udev                              10240        0     10240   0% /dev
 tmpfs                            830924     1572    829352   1% /run
 /dev/disk/by-uuid/<UUID of sdb1> 474440   257750    192193  58% /
 /dev/sdb5                      48062440 10100468  35520496  23% /home
 /dev/sdb6                      28834716  4261084  23108908  16% /usr
 /dev/sdb7                      38448276  2373524  34121652   7% /var
 /dev/sdb8                      19228276   994244  17257284   6% /tmp
 /dev/sdb9                      38448276 12808004  23687172  36% /usr/local
 /dev/sdb12                     96124904 11577368  79664584  13% /info
 /dev/disk/by-uuid/<UUID of sdb1> 474440   257750    192193  58% /
 /dev/sdb13                    192243928 58177436 124300984  32% /storage

My / usage is still huge, 258 Mb, but at least the "full" problem is gone.
I hope I can ignore the doubly mounted root partition.

It is no problem. The new Mageia/kernel/mount tends to do that-- No idea why.

Try du --max-depth 2 -x /
to find which directories are problematic for size.


Haines



Reply to: