partition not using full space
okay I did a cf disk and noticed something pretty good for my situation. My root partition says it's full.
This is what I get when I type "df" Code:
Filesystem 1K-blocks Used Available Use% Mounted on Code:
|
Try writing a large file to your root partition and see if it goes OK. I had this happen once and I could keep writing files to the partition which was under reported in df with 100% usage. It just kept expanding the reading in df always reporting 100% usage. It then mysteriously disappeared and gave the correct readings in df. I believe I used pm on that partition too. PM writes partition info to the mbr differently than linux based partitioning tools. Perhaps cfdisk can read this info correctly but df can not.
|
df is just reading the size wrong. if that filesystem was full, programs would be crashing.
|
and they do! it got to the point where Gnome wouldn't start up! I deleted some files on my root partition and it got in there. and no it's not reading it wrong becuase since I've added to the partition I haven't added more than 100MB to it.
Also my Gnome isn't loading in new users I create... EDIT: Also my cookies aren't saving like my logins to different forums including this one. When I go into the Firebird Preferences and make changes and click OK I got something saying that the changes couldn't be saved and won't be taking effect the next time I open the browser.... Also I rebooted and did another 'df' and it didn't even show the root partition; it only showed my home partition |
This goes with the standard warning of "have backups"
Anyway, resizing the partition is only part of your job. :) You need to resize the file system also... e2fsck -f /dev/hda2 resize2fs /dev/hda2 |
hm I got like a bunch of stuff with inodes it was ongoing do I press 'y' or 'n' ?
|
Did you remember to do this in an un-mounted condititon?
I like to boot up with the system rescue cd and run things like that. |
it looks like you have room to backup your root to your home, then reformat root, and
then restore the stuff. that should take care of it. |
And in the future, you may want to consider definining other partitions explicitly. I've got a dual boot Windows and Linux machine on a single 40G drive, and this is my scheme:
/dev/hda1 = Windows (12G) primary /dev/hda2 = /boot (100Mg) primary /dev/hda3 = swap (256Mg) primary /dev/hda4 = [----] logical /dev/hda5 = / (1G) /dev/hda6 = /usr (10G) /dev/hda7 = /tmp (1G) /dev/hda8 = /var (1G) /devhda9 = /root (1G) /dev/hda10 = /home (13G) That may be overkill, but it works for me. Partitioning is highly personal though, and there is no necessarily "right" or "wrong" way to do it, it pretty much boils down to what works best for you. -- J.W. |
yeah I just decided I'd reinstall Slackware with version 9.1 it got all F'ed up it was crazy lol
anyway here's my new df Code:
Filesystem 1K-blocks Used Available Use% Mounted on |
All times are GMT -5. The time now is 06:59 AM. |