**** BEGIN LOGGING AT Wed Feb 29 02:59:58 2012 Feb 29 08:55:19 hello, I've been playing with my Fonera 2.0n (with very low *nix knowledge) and now when I try to edit a file it says "no space left" Feb 29 08:55:32 any hint to solve this? :\ Feb 29 08:56:39 I was editing a script file in /etc/init.d Feb 29 08:56:55 that's it Feb 29 08:57:58 even renaming a file returns "no space left on device" Feb 29 08:59:26 root@Fonera:/etc/init.d# df -h Filesystem Size Used Available Use% Mounted on rootfs 4.6M 4.6M 0 100% / /dev/root 4.6M 4.6M 0 100% /rom tmpfs 512.0k 0 512.0k 0% /dev /dev/mtdblock6 2.1M 2.1M 76.0k 97% /jffs mini_fo:/jffs 4.6M 4.6M 0 100% / \134\134192.168.11.2\134shares Feb 29 09:20:00 Seems you really have no space left (you should check the "Mounted on /jffs" partition) Feb 29 09:20:30 or actually, you seem to have 76K left, but perhaps that's just not enough Feb 29 09:22:04 uh... could you please suggest something safe to delete? let's say logs or something.... Feb 29 09:22:20 You can try removing some files to save space, but note that only files that were added after flashing the firmware help here (files that are in the base firmware are stored in a big read-only partition, so you cannot really remove them, instead the /jffs partition just records the deletion) Feb 29 09:22:43 btw the symlink is created at startup now, thanks again ;) Feb 29 09:22:58 Logs (anything in /tmp and /var) are stored in RAM, so they don't take up any space in /jffs Feb 29 09:23:47 If you're out of space, it's because of files you've added yourself. You can look around /jffs (for example, use "find /jffs") to see which those files are. Feb 29 09:26:46 uhm I don't remember adding anything yesterday when it has started to happen all this out of space stuff.... let me check jffs... Feb 29 09:28:36 Also, a reboot could perhaps help (I think sometimes freed space is not completely reclaimed until a reboot) Feb 29 09:29:07 jffs/mnt/shares/FoneraApps/mediatomb.2.3.7.0.fmg Feb 29 09:29:15 is this supposed to be there? Feb 29 09:30:26 uhm it is just a link... Feb 29 09:30:32 reboot didn't help Feb 29 09:31:59 uhm no... it is not a link Feb 29 09:32:14 for some reasons this file ended there Feb 29 09:33:03 I'm trying removing it and rebooting Feb 29 09:33:38 bingo Feb 29 09:33:45 reboot wasn't needed :) Feb 29 09:33:48 ty!! Feb 29 09:34:57 welcome Feb 29 09:35:14 I suspect it got added there at some point where your samba link wasn't working Feb 29 09:35:31 for that reason, you might want to consider mounting in /tmp/shares instead of /mnt/shares Feb 29 09:36:08 but I ended up having a wiped out hdd :) Feb 29 09:36:46 tmp/mounts/Disc-A1 actually Feb 29 09:36:49 I mean, still use the symlink trick, but use /tmp instead of /mnt Feb 29 09:37:01 I haven't tried yet on /tmp/shares to be correct Feb 29 09:37:50 the /tmp/ dir scares me now :D Feb 29 09:38:10 Well, /tmp is not actively wiped, it's just not stored Feb 29 09:38:40 (it's a tmpfs that's stored in ram, so on a reboot, the Fonera just forgets about the files in /tmp) Feb 29 09:39:01 I can imagine that there is something that actively wipes /tmp/mounts, though Feb 29 09:39:25 uhm, I see... and that could explain the mounted hdd wiped out Feb 29 09:45:25 Having said that: I couldn't find the code that actively wipes /tmp/mounts when I looked for it last week, but I didn't spend so much time on it Feb 29 09:46:36 and don't spend any more time on it Feb 29 09:47:13 lesson learned - /tmp/mounts/ left alone :) **** ENDING LOGGING AT Thu Mar 01 02:59:59 2012