Bug #2449
closed
Console "Filesystem is full" on NanoBSD version
0%
Description
Tried to upgrade the NanoBSD embedded version and now getting an error on console saying /tmp write failed: Filesystem is full. I have tried reinstalling from a fresh image, and the latest images have the same issue. When dropping into an SSH session it seems like /tmp is at 100% full. The system is now dead slow, and the web gui is not working.
The last version to work was a build on the 18th May. Since then none of the new builds are working.
Updated by Jim Pingle over 13 years ago
- Status changed from New to Feedback
- Priority changed from Urgent to Normal
Not nearly enough information here - specifically we need to know at least what size nanobsd image you're running and what packages you have installed. This really belongs in a forum post until an actual bug is confirmed.
Updated by Warren Bird over 13 years ago
Apologies for not giving more information Jim. Let me tell you what ive done:
1. I am currently running a build from the 18th May - built on Fri May 18 05:21:05 EDT 2012. I am running a 2G NanoBSD version of 2.1
2. I have tried upgrading from within the GUI, but as soon as I do that the system reboots, and then does not come back online due to the error that /tmp is full.
3. I thought that this might be an issue with the upgrade, so decided to try a 2G and 4G nanoBSD image (fresh install) - but both of these seem to have the same issue. /tmp is full from the console. When trying to get into the GUI on either of these fresh installs it doesnt allow me to get in. It just comes up with an error in the console, followed by multiple errors showing /tmp is full.
4. The packages that were being run on the system when I tried to upgrade, was Squid and Sarg.
I am more than happy to put this into a forum, but just thought that everyone else using the 2G or 4G nanoBSD images would be having a similar problem.
Updated by Jim Pingle over 13 years ago
- Status changed from Feedback to Closed
I just updated a NanoBSD install and it's fine, /tmp is at 0% used. GUI login is OK.
I'd have to guess that squid and/or sarg are doing something bad there.
I'd definitely move this to the forum to gather more definitive data and to see if anyone else has similar issues.