On Saturday 25 February 2006 01:08, Istvan Gabor wrote:
Hello all:
I have the following problem with my suse 10.0 OSS with kde 3. 4.
I wanted to install my own freedb database. For this purpose I created a separate partition with 10 GB size. I exctracted the tar archive to this partition. The extraction took a really long time, for hours so I left the machine alone. After the extraction has finished tar gave some error messages that could not extract everything since no space left on the drive. However df -h showed this: df -h Filesystem Size Used Avail Use% Mounted on /dev/sda4 9.2G 4.9G 3.9G 56% /home/user/sda4
After rebooting the computer I found that my lilo was corrupted that I had to fix using the rescue boot disk. When I was able login in again I wanted to create new directories on the abovementioned drive but I got this error message:
mkdir sda4/temp mkdir: cannot create directory `sda4/temp': No space left on device
However df -h shows the same as above: df -h Filesystem Size Used Avail Use% Mounted on /dev/sda4 9.2G 4.9G 3.9G 56% /home/user/sda4
When I run fsck.ext3 (with /dev/sda4 unmounted) it does not report any error: fsck.ext3 /dev/sda4 e2fsck 1.38 (30-Jun-2005) /dev/sda4: clean, 1221600/1221600 files, 1301070/2441880 blocks
Now I don't know what the problem is and how I could fix it. Any help would be appreciated. Thanks, IG
Hello IG, I just had the same problem a few days ago. I have a separate partition for home and backup. For some reason they didn't mount automatically on reboot. So when I ran rsync to update my system everything was backed up to my root partition. It is small and filled up completely. I couldn't login graphically. I managed to login on the command line. I used this command: du -hsx /* to find out where on my root partition the unwanted data was and I removed it. Them I mounted the home and backup partitions and everything is fine. I hope this helps, Jerome