Just had this problem again. 32-bit 9.04 fresh install with all updates on HP DL380G3. Built the machine just to run scrub against some drives to see if any were dead. Drives filled, I rebooted, deleted all the scrub files (so there's about 93GB free) and went to HP's site to download some firmware, which failed due to lack of temp space. "overflow" was mounted at /tmp with a size of 1MB. Tried to "/etc/init.d/mountoverflowtmp stop", which doesn't actually remove that /tmp mount. "/etc/init.d/mountoverflowtmp start" just causes it to report a second mounting. Another reboot put things back to normal.
BTW, these are all EXT2 filesystems this time. /dev/cciss/c0d0p1 on / type ext2 (rw,relatime,errors=remount-ro) tmpfs on /lib/init/rw type tmpfs (rw,nosuid,mode=0755) proc on /proc type proc (rw,noexec,nosuid,nodev) sysfs on /sys type sysfs (rw,noexec,nosuid,nodev) varrun on /var/run type tmpfs (rw,nosuid,mode=0755) varlock on /var/lock type tmpfs (rw,noexec,nosuid,nodev,mode=1777) udev on /dev type tmpfs (rw,mode=0755) tmpfs on /dev/shm type tmpfs (rw,nosuid,nodev) devpts on /dev/pts type devpts (rw,noexec,nosuid,gid=5,mode=620) fusectl on /sys/fs/fuse/connections type fusectl (rw) lrm on /lib/modules/2.6.28-13-generic/volatile type tmpfs (rw,mode=755) /dev/cciss/c0d1p1 on /disk1 type ext2 (rw,relatime) /dev/cciss/c0d2p1 on /disk2 type ext2 (rw,relatime) securityfs on /sys/kernel/security type securityfs (rw) binfmt_misc on /proc/sys/fs/binfmt_misc type binfmt_misc (rw,noexec,nosuid,nodev) gvfs-fuse-daemon on /home/cmccabe/.gvfs type fuse.gvfs-fuse-daemon (rw,nosuid,nodev,user=cmccabe) Filesystem Size Used Avail Use% Mounted on /dev/cciss/c0d0p1 101G 2.3G 93G 3% / tmpfs 1.9G 0 1.9G 0% /lib/init/rw varrun 1.9G 108K 1.9G 1% /var/run varlock 1.9G 0 1.9G 0% /var/lock udev 1.9G 148K 1.9G 1% /dev tmpfs 1.9G 88K 1.9G 1% /dev/shm lrm 1.9G 2.2M 1.9G 1% /lib/modules/2.6.28-13-generic/volatile /dev/cciss/c0d1p1 67G 52K 64G 1% /disk1 /dev/cciss/c0d2p1 68G 52K 64G 1% /disk2 Linux cmccabe-dl380 2.6.28-13-generic #44-Ubuntu SMP Tue Jun 2 07:57:31 UTC 2009 i686 GNU/Linux Without taxing my under-caffeinated brain too much, can someone explain the point of mounting this puny /tmp in the first place? Is this a ramdrive so even if the disks are truly full, progs can still see "temp" space? I think the cure is worse than the ill. Furthermore, I think it contradicts what so many people like about the 'nix world: the straightforward approach. If the disk is full, the system should tell you the disk is full, not try to fake it so things half work. Thanks, Chaz -- /tmp is not automatically resized until system restart https://bugs.launchpad.net/bugs/285096 You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. -- ubuntu-bugs mailing list [email protected] https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
