Hello,
Recently started having a problem with my VeraEdge where it complains that Luup engine is taking longer to reload. I started following the guide at http://forum.micasaverde.com/index.php/topic,29608.msg211785.html#msg211785, but when trying to move the latest user_data.json.lzo file, the edge complains that:
mv: can't rename 'user_data.json.lzo': No space left on device.
Running the command df -h gives the output:
Filesystem Size Used Available Use% Mounted on
rootfs 9.4M 9.2M 204.0K 98% /
/dev/root 9.5M 9.5M 0 100% /rom
tmpfs 61.9M 7.2M 54.7M 12% /tmp
/dev/mtdblock6 9.4M 9.2M 204.0K 98% /overlay
overlayfs:/overlay 9.4M 9.2M 204.0K 98% /
tmpfs 512.0K 0 512.0K 0% /dev
I’m not too familiar with Linux, but presumably this confirms I’ve run out of space. Any suggestions?
Well, yes.
Mine for comparison (UI5, VeraLite)
Filesystem 1K-blocks Used Available Use% Mounted on
/dev/root 4608 4608 0 100% /rom
tmpfs 31240 2976 28264 10% /tmp
tmpfs 512 0 512 0% /dev
/dev/mtdblock7 11264 2356 8908 21% /overlay
overlayfs:/overlay 11264 2356 8908 21% /
/dev/mtdblock8 4480 4480 0 100% /mios
What HAVE you put on there?
Need more info …
Try the commands:
cd /
du -s * | sort -n
The output for me is:
0 dev
0 mnt
0 proc
0 root
0 sys
0 var
1 mios_constants.sh
442 www
499 sbin
635 bin
2055 overlay
3984 tmp
4680 storage
6815 etc
8401 lib
14104 usr
15234 mios
24196 rom
Thanks for the replies everyone. Output from that command is:
root@MiOS_45003650:~# cd /
root@MiOS_45003650:/# du -s * | sort -n
0 dataMine
0 dev
0 mios
0 mnt
0 proc
0 root
0 storage
0 sys
0 var
499 sbin
635 bin
2370 www
7091 lib
7380 tmp
8264 etc
10205 overlay
15373 usr
24196 rom
the etc directory contains config info and downloaded plugin files.
You may want to cd to the the overlay directory to see what is using all the extra space. Issue the same du command.
You may need to do this one more level if you find one big sub directory. Post your results so we (I) can compare with my system.
Hi everyone,
I’ve had a look at the overlay directory and a few sub directories, and it appears that the file /overlay/etc/cmh-firmware/mios.squashfs is taking up a lot of space. Presumably this is my problem?
Thanks for the help again. Its appreciated!
root@MiOS_45003650:/overlay# du -s * | sort -n
0 dataMine
0 mnt
0 root
0 storage
49 sbin
60 usr
2333 www
7764 etc
root@MiOS_45003650:/overlay# cd www
root@MiOS_45003650:/overlay/www# du -s * | sort -n
0 upnp
0 wizard
1 cgi-bin
19 cmh
2314 dm
root@MiOS_45003650:/overlay/www# cd dm
root@MiOS_45003650:/overlay/www/dm# du -s * | sort -n
0 dataMineWeb.tar.gz
2 index.html
6 dataMine.css
14 graph.html
89 images
333 js
1870 extjs
root@MiOS_45003650:/overlay/www/dm# cd /overlay/
root@MiOS_45003650:/overlay# cd etc
root@MiOS_45003650:/overlay/etc# du -s * | sort -n
0 alerts
0 cmh-backup
0 cmh-lu
0 cmh-static
0 cmh-zwfw
0 crontabs
0 ethers
0 gcom
0 mios
0 rc.d
0 zwave-aes
1 TZ
1 TZ-full
1 Wireless
1 cmh-ra
1 dropbear
1 firewall.user
1 host_ip
1 init.d
1 mios_backup.info
1 mios_backup.info.old
1 passwd
1 shadow
3 hosts
4 uci-defaults
5 cmh.factory.default
5 hotplug.d
16 config
45 usb-mode.json
230 cmh
310 cmh-ludl
7140 cmh-firmware
root@MiOS_45003650:/overlay/etc# cd cmh-firmware/
root@MiOS_45003650:/overlay/etc/cmh-firmware# du -s * | sort -n
1 mios-hooks.sh.md5
24 mios-hooks.sh
7116 mios.squashfs
root@MiOS_45003650:/overlay/etc/cmh-firmware# ls -l
-rw-r--r-- 1 root root 23582 Jul 5 06:57 mios-hooks.sh
-rw-r--r-- 1 root root 33 Jul 5 06:57 mios-hooks.sh.md5
-rw-r--r-- 1 root root 7286784 Jul 5 07:01 mios.squashfs
root@MiOS_45003650:/overlay/etc/cmh-firmware#
FWIW, my Edge reports this:
root@MiOS_45101161:/overlay# du -s * | sort -n
0 nas
0 storage
1 mios_constants.sh
2 eventWatcher
8 root
120 usr
438 www
505 lib
1964 etc
root@MiOS_45101161:/overlay# cd www
root@MiOS_45101161:/overlay/www# du -s * | sort -n
0 wizard
1 DataWatcher.conf
1 favicon.ico
1 index.html
1 luaupnp.xml
1 upnp
27 cgi-bin
408 cmh
I have certainly seen the the dataMine /www/ tree (with all its JavaScript libraries) takes up a lot of space (so I don’t use it any more.)
If you collect data on your Vera you should make sure it is going to a USB disk!
http://forum.micasaverde.com/index.php?topic=27841.0
Reading that it would appear I am safe to delete that file?
If you delete that file … you will not likely have room for the next upgrade … since the upgrade will need that much space or more.
What about the newmios.squashfs file in /tmp/?
root@MiOS_45003650:/tmp# du -s * | sort -n
0 alerts
0 dhcp.leases
0 dnsmasq.d
0 hosts
0 lock
0 log
0 opkg-lists
0 overlay
0 usr
4 RT2860.dat
4 TZ
4 etc
4 log.lighttpd_error
4 newmios.squashfs.md5
4 resolv.conf
4 resolv.conf.auto
8 state
8 sysinfo
12 log.mios_firmware
16 user_data.json.lzo.swp
24 run
7272 newmios.squashfs
It should disappear when you power cycle.
/tmp is a file system that uses a different type of memory.
You should be able to delete that file …
Guys, thanks for this thread. Came in handy when my UI7/Edge was experiencing very odd symptoms. Turns out it was Datamine logs - so now reset that lot.
One question I’ve got though, comparing my usage to others above is can I delete the ROM directory ?
/# du -s * | sort -n
0 dev
0 mnt
0 proc
0 root
0 sys
0 var
1 mios_constants.sh
2 eventWatcher
13 storage
499 sbin
635 bin
2802 www
3660 tmp
3990 etc
8401 lib
11989 dataMine
14096 usr
14271 mios
18307 overlay
24196 rom
cd into ROM shows…
rom# du -s * | sort -n
0 dev
0 mios
0 mnt
0 overlay
0 proc
0 root
0 sys
0 tmp
0 var
1 rom
37 www
499 sbin
582 etc
635 bin
8401 lib
14042 usr
If you delete the ROM directory … Vera will not have any software to run or boot!
You’d think…but why doesn’t the ROM directory feature on any of the lists from other members above ??