[Discuss] MyBookLive disk space issues

[Jerry Feldman]

I've got a WD MyBook at work. I am surprised that /DataVolume is not
RAID, but based on my experience, MyBook uses Busybox. I added some
software from optware. In any case, you will need to manually drill down
the root files system /dev/md1 and try to find out where the larger
files are and manually delete them. After you locate the culprits, you
might want to check out optware for some of the commands that BusyBox is
missing (or brain dead). You might find that MyBook Live is not rotating
the logs.

On 02/17/2012 07:34 PM, Doug wrote:
> I bought a MyBookLive for the family media collection. I like that
> they are using open source software on the device. I am able to ssh
> over there and reboot for example when that is needed.
>
> I got a message that a file was not able to be written. So I ran this command:
>
> MyBookLive:~# df -h
> Filesystem            Size  Used Avail Use% Mounted on
> /dev/md1              1.9G  1.9G     0 100% /
> tmpfs                  50M     0   50M   0% /lib/init/rw
> udev                   10M  6.7M  3.4M  67% /dev
> tmpfs                  50M     0   50M   0% /dev/shm
> tmpfs                  50M  2.7M   48M   6% /tmp
> ramlog-tmpfs          1.9G  1.9G     0 100% /var/log
> /dev/sda4             924G  531G  393G  58% /DataVolume
>
> 100%, not a good sign. Where are the problems?
>
> MyBookLive:/# du -sh var
> 1.5G	var
>
> Let's look in there:
>
> MyBookLive:/# du -sh var/*
> 4.0K	var/backups
> 1.3M	var/cache
> 15M	var/lib
> 52K	var/local
> 0	var/lock
> 946M	var/log
> 4.0K	var/log.hdd
> 4.0K	var/mail
> 4.0K	var/opt
> 0	var/run
> 12K	var/spool
> 0	var/tmp
> 0	var/twonkymedia
> 542M	var/www
>
>
>
> MyBookLive:/# du -sh --si var/*
> 4.1k	var/backups
> 1.4M	var/cache
> 15M	var/lib
> 54k	var/local
> 0	var/lock
> 992M	var/log
> 4.1k	var/log.hdd
> 4.1k	var/mail
> 4.1k	var/opt
> 0	var/run
> 13k	var/spool
> 0	var/tmp
> 0	var/twonkymedia
> 568M	var/www
>
> I am not seeing it (the --si follows symbolic links).
>
> MyBookLive:/var# ls -lah
> total 48K
> drwxr-xr-x 12 root root 4.0K Nov 14  2011 .
> drwxr-xr-x 25 root root 4.0K Dec 31 19:17 ..
> drwxr-xr-x  2 root root 4.0K Feb 17  2012 backups
> drwxrwxrwx 10 root root 4.0K Nov 14  2011 cache
> drwxr-xr-x 28 root root 4.0K Nov 14  2011 lib
> drwxr-xr-x  4 root root 4.0K Nov 14  2011 local
> lrwxrwxrwx  1 root root    4 Nov 14  2011 lock -> /tmp
> drwxr-xr-x  7 root root 4.0K Dec 31 19:03 log
> drwxrwxrw-  2 root root 4.0K Nov 14  2011 log.hdd
> drwxr-xr-x  2 root root 4.0K Nov 14  2011 mail
> drwxr-xr-x  2 root root 4.0K Nov 14  2011 opt
> lrwxrwxrwx  1 root root    4 Nov 14  2011 run -> /tmp
> drwxr-xr-x  3 root root 4.0K Nov 14  2011 spool
> lrwxrwxrwx  1 root root    4 Nov 14  2011 tmp -> /tmp
> lrwxrwxrwx  1 root root   24 Nov 14  2011 twonkymedia ->
> /CacheVolume/twonkymedia
> drwxr-xr-x  6 root root 4.0K Nov 14  2011 www
>
> How should I be looking for who is eating up all the disk space? Is
> there a general command to limit cache or logs? I guess I am not much
> of a sys admin.
>


-- 
Jerry Feldman <gaf at blu.org>
Boston Linux and Unix
PGP key id:3BC1EB90 
PGP Key fingerprint: 49E2 C52A FC5A A31F 8D66  C0AF 7CEA 30FC 3BC1 EB90