[mythtv-users] root partition filled up -- no space to start mysqld

[Dewey Smolka]

>
> Unmount these 3 filesystems to expose their mountpoints on /dev/sda, and run
>
> # du -hscx /*
>
> as George has suggested. I'd be interested if the numbers you get from
> this are different to those you posted earlier.

Bingo. I'm not sure how this happened, but here's what I'm getting:

[root at mythbackend sdb2]# mount
/dev/sda2 on / type ext3 (rw)
proc on /proc type proc (rw)
sysfs on /sys type sysfs (rw)
devpts on /dev/pts type devpts (rw,gid=5,mode=620)
/dev/sda1 on /boot type ext3 (rw)
tmpfs on /dev/shm type tmpfs (rw)
none on /proc/sys/fs/binfmt_misc type binfmt_misc (rw)
sunrpc on /var/lib/nfs/rpc_pipefs type rpc_pipefs (rw)
nfsd on /proc/fs/nfsd type nfsd (rw)
[root at mythbackend sdb2]#

All the extra filesystems, including sda5 are unmounted.

[root at mythbackend sdb2]# du -hscx /*
5.7M    /bin
6.1M    /boot
88K     /dev
68M     /etc
74M     /home
82M     /lib
16K     /lost+found
8.0K    /media
8.3G    /mnt
4.0K    /mythextra
4.0K    /mythlibrary
4.0K    /mythlibrary2
14M     /opt
du: cannot access `/proc/32060/task/32060/fd/4': No such file or directory
du: cannot access `/proc/32060/task/32060/fdinfo/4': No such file or directory
du: cannot access `/proc/32060/fd/4': No such file or directory
du: cannot access `/proc/32060/fdinfo/4': No such file or directory
0       /proc
368K    /root
16M     /sbin
4.0K    /selinux
4.0K    /srv
7.1M    /storage
0       /sys
67M     /tmp
2.5G    /usr
225M    /var
12G     total
[root at mythbackend sdb2]#

Everything's being eaten up by /mnt.

/mnt contains: mythremotestorage (a legacy mount point for nfs storage
borrowed from my desktop), currently unmounted and empty.
/sdc2: mountpoint for sdc -- empty
/sdb2: mountpoint for sdb. Should be empty but here's what I found:

[root at mythbackend sdb2]# ls -l
-rw-r--r-- 1 root root 1919606784 2008-05-20 08:09 3264_20080519220000.mpg
-rw-r--r-- 1 root root 6897453056 2008-05-19 21:45 3640_20080519184800.mpg
-rw-rw-rw- 1 root root     111174 2008-05-20 08:10 3640_20080519184800.mpg.png
[root at mythbackend sdb2]#

There's all the missing space alright. But I'm a little confused as to
why it got there and why it's owned by root.

I don't recall ever launching mythfrontend as root, although it's
certainly possible. But I'm quite sure I didn't do last night.

Thanks for the help. I'm happy I've found the problem, but still have
no idea how it happened or what I'll need to do to stop it from
happening again.

I'll go back and double check my settings, and I may put that new
drive (both, actually) through some paces while it's still returnable
to make sure it's not a hardware issue.

Thanks again, but do you have any idea why this might have happened?

I appreciate the help.