"Raimund Berger" <[email protected]> writes:
> Addition: > > just came to think, 'remountrw' won't suffice. > > You'd need to get rid of the /rw tmpfs mount, which will likely be busy > though. Only way around that would be shutting down all processes which > access it (or one of the symbolic links pointing to it, like /tmp) and > then unmount it. > > Those processes can found with 'lsof', which hopefully is already > installed on your system. An alternative is 'fuser'. > > Good luck, R. OK, sorry for the flood, but a final remark. You can mount the actual (disk) root file system a second time, but just read only. Example: mount -t ext2 -r /dev/disk/by-label/ROOT_FS /mnt After that, 'df' should show /mnt also being 100% full, but this time you can see what the disk file system really looks like, under /mnt. You won't be able to change it though, due to the read only mount. But if you find stuff which eats up space excessively you can at least proceed as said earlier, i.e. get rid of the tmpfs if necessary, remount the root fs writable and then delete. If 'du' still says ~600MB on /mnt though it could be the file system is really corrupt, although that shouldn't be possible because it'd get checked on boot. But, while / being mounted read only, you could try to force a check anyway e2fsck -f /dev/disk/by-label/ROOT_FS see if that freed any space and best reboot afterwards. OK, that's about all I got to say I guess ;) _______________________________________________ Voyage-linux mailing list [email protected] http://list.voyage.hk/mailman/listinfo/voyage-linux
