Disk space usage (/) 19Gb, 4363Mb used 98% full.
Hi, I have just upgraded my system to 2010, by adding a new 500Gb HD and partitioning it for separation of files.
I get this bogus error message. (something like) Disk space usage (/) 19Gb, 4363Mb used, 98% full. I have numerous partitions, here is my fstab....with sizes... Code:
# Entry for /dev/sda5 :19Gb Code:
glenn@GamesBox:~$ df (19-11 14:36) As /boot, /tmp, /var, /usr and /home are on separate partitions I feel this is a false positive, but running a few checks, to be sure, to be sure, have not been able to resolve the issue. At the moment I can not install any more packages, even small ones (4kb) I have run fsck -pfv, but received the same size info. I have also checked symlinks and ldconfig (hoping) to no avail. This is abnormal, But I don't know how to fix it without formatting and reinstalling. Any suggestions would be appreciated. Thank you, Glenn |
Hi -
It's probably *not* a false positive. It definitely sounds like you're using 20GB of 20GB in your root ("/") partition. By all means - please check "/dev", "/mnt". It's common to accidentally write large files to one of these directories by mis-typing a device name, or failing to actually mount a separate partition as expected. Failing all else, another strategy to find the culprit is: a) Go into single-user mode b) *Unmount* all your partitions *except* "/" c) Run "du -s" again to identify any (unexpected) space hogs |
You may also have a hidden ".Trash" folder on a partition(s) which may have deleted files just sitting there. Was the /tmp folder always on another partition, or was it on root (/) partition for some time before it was moved to another partition, if it was, then there maybe some files that were never deleted first, so they will still be taking up space.
|
Thank you for the suggestions,
It very well may have been a stale .Trash dir. /tmp has always been on it's own partition. I had no joy with those and re-formatted and reinstalled. First time in a while I've had to do that. here is the output of df Code:
[root@GamesBox glenn]# df Regards Glenn |
ext4 fs, could it be because of?
Hi again, the issue has not been solved by reformatting.
Over night, I attempted to re-build my kernel, and it erred out during compilation. "disk full"... Code:
ld: final link failed: No space left on device Code:
glenn@GamesBox:/usr/src$ du -s (20-11 07:55) Code:
glenn@GamesBox:/usr/src$ df (20-11 08:10) When dissecting /usr/src, there are some large files, like...du Code:
2.6G ./linux-2.6.31.5-1mnb/drivers ... I wonder if everything is just 10 times larger than it is supposed to be. I'm going to try it again, by formatting /usr/src as ext3 Because it has not happend on my system b4 I used ext4. I upgraded to Mandriva 2010.0 last week, and had no such problems, Until I reformatted to ext4, which seems quite speedy . :-) Still looking.... Glenn |
Hi, I tried again and had a similar outcome, the 5gig partition was nearly filled.
Perhaps I never realised just how much space was required by re-building a kernel, As I have only just started to use a separate partition for /usr/src when this occurred. Make clean cleans it up.... using df before make clean /dev/sda15 5.0G 4.8G 0 100% /usr/src after make clean /dev/sda15 5.0G 455M 4.3G 10% /usr/src Of course this is after the kernel has been re-configured, compiled and installed. Who knows? cheers Glenn |
That is strange, I have compiled kernels many times, and most are usually around 700-900mb, that seems to be excessively large. My last kernel I compiled was 2.6.31.4 and it is only 895mb.
|
Hi, Thanks fotoguy, That looks better.
I also switched back to ext4 and there was no difference. I tried a cooker kernel, Code:
glenn@GamesBox:~$ uname -a Maybe it's a tool used for compiling, it's ok now, just an anomaly(?). cheers, Glenn |
All times are GMT -5. The time now is 07:03 PM. |