NETGEAR is aware of a growing number of phone and online scams. To learn how to stay safe click here.
Forum Discussion
System volume root usage (/dev/md0) at 100%
I have recently began getting the error message in logs “Volume: System volume root's usage is 100%. This condition should not occur under normal conditions. Contact technical support.”
Some se...
tommyhackett wrote:
16M chunk-stream0-00821.m4s
16M chunk-stream0-00689.m4s
16M chunk-stream0-00601.m4s
16M chunk-stream0-00466.m4s
15M chunk-stream0-00833.m4s
Delete all of these chunk files. They are remnants of plex real-time transcoding - they really shouldn't be writing them to the root, but that's something to take up with the plex folks.
Are there more of these? The four in your post don't account for all of the space use (only ~80 MB of it).
tommyhackett wrote:
root@TXHReadyNAS://# du -hsx * | sort -rh | head -10
du: cannot access 'proc/15544/task/15544/fd/3': No such file or directory
du: cannot access 'proc/15544/task/15544/fdinfo/3': No such file or directory
du: cannot access 'proc/15544/fd/3': No such file or directory
du: cannot access 'proc/15544/fdinfo/3': No such file or directory
948M apps
apps is actually a mount point to the data volume, so it isn't part of the problem here. The "du" errors are also related to mount points.
It's best to remount the root volume, and search that - it avoids these issues, and can uncover space usage that is hidden underneath mount points. It's also much faster.
So start by entering
mount --bind / /mnt
That mounts sysroot as /mnt.
Then analyze space on /mnt
When done, you unmount it with
cd / umount /mnt
The cd matters, the umount will fail if you are in a folder of /mnt.
Hi, thanks for the response. I did a little more searching just after I made the post and think I'm in a good place now.
You're right, there were more of the chunk files (1461 written to the root!) and removing them appears to have solved my problem.
After doing that, I think I'm ok with root looking like:
root@TXHReadyNAS:~# cd /
root@TXHReadyNAS:/# ls -1
1
apps
bin
boot
data
dev
etc
frontview
home
init-stream0.m4s
init-stream1.m4s
lib
lost+found
media
mnt
opt
proc
root
run
sbin
selinux
srv
sys
tmp
usr
var
root@TXHReadyNAS:/# df -h
Filesystem Size Used Avail Use% Mounted on
udev 10M 4.0K 10M 1% /dev
/dev/md0 3.7G 649M 2.9G 19% /
tmpfs 1009M 8.0K 1009M 1% /dev/shm
tmpfs 1009M 468K 1009M 1% /run
tmpfs 505M 1000K 504M 1% /run/lock
tmpfs 1009M 0 1009M 0% /sys/fs/cgroup
/dev/md127 1.9T 729G 1.2T 40% /data
/dev/md127 1.9T 729G 1.2T 40% /home
/dev/md127 1.9T 729G 1.2T 40% /apps
I'm really not sure what could have caused Plex to behave this way initially, perhaps I did something wrong when installing/updating it some time. Any way, I have removed and reinstalled Plex using the GUI. No signs yet that it is writing unwanted stuff to the root again, but I will have to keep an eye on it I guess.
You should probably remove these two also, as they were also left there by plex.
init-stream0.m4s init-stream1.m4s
Ah ok, I have done that now, thanks!
NETGEAR Academy
Boost your skills with the Netgear Academy - Get trained, certified and stay ahead with the latest Netgear technology!
Join Us!
