# System Falsely Reports 0 Bytes Free On Hdd

The notification system reports zero bytes free on my hdd. Also, tracker does not appear to be running. I have a dual boot system: Win10/Fed24/Gnome3. How can I get the system to properly report the free space I have left. It should be about 300GB. Do I need to start tracker manually, deleted indexes or something else.

edit retag close merge delete

Please edit your question to include the output from df so that we can see how much space there really is. Also, remember that 5% of each partition is reserved by default to provide a little wiggle room for emergencies.

( 2016-11-21 16:05:15 -0500 )edit

install Gparted on fedora to have a clearer view of your space and how its partitioned you can easily edit your space from there

( 2016-11-22 08:08:39 -0500 )edit

Hi. Recently, I had a similar problem, I don't know if it's your case, but I'tell you because it could be useful for you. My problem was caused by a bug of the ROM of the motherboard that caused the system write a lot of data (errors) on the /var/kern.log file, resulting on a huge file with GB of size. I could solve it with an update of the ROM.

( 2016-12-16 06:48:18 -0500 )edit

Sort by » oldest newest most voted

This happened again after I rebuilt the system from scratch. Fortunately, I had a backup image stored on a usb hdd, that I recovered with Clonezilla.

It appears that my problem was caused by an improperly constructed "dd" command, which I was using to wipe a usb stick that had stopped working.

PLEASE DO NOT USE ANY OF THE FOLLOWING UNLESS YOU KNOW WHAT YOU ARE DOING

I had constructed the dd command as follows:

dd if=/dev/zero of=sdb  #Where sbd is the usb stick.


Apparently the result of this was to fill all the available space on "sda" with zeros.

I believe the dd command should have been constructed in the following manner:

dd if=/dev/zero of=/dev/sdb


I suspect this would have saved me a lot of grief. The next time I try this it will be from a LIVE distro and I will be sure to have a recent backup image.

more

The first command would have overwritten a regular file named "sdb" in the current directory you executed it from. As executed, dd would have written zeros to this file, continually making it larger until the filesystem the current directory was a part of ran out of space. The first command is the equivalent of "dd if=/dev/zero of=(current directory)/sdb count=(infinity)". The file "sdb" in the (current directory) is not the same as the "special block" file "sdb" in the /dev directory unless the (current directory) you are in is actually "/dev". It also wouldn't wipe the stick!

( 2016-12-16 17:23:36 -0500 )edit