Welcome to Serverfault.

• If you didn't reboot : You should probably use : lsof -a +L1 can help you find out which deleted (rm'd) files still have opened "file handles" (ie, some program still points to it and thus the file itself is not deleted yet from the filesystem, even though its last name entry has been deleted by rm). The offset will hint at the largest files amongst them. If you see one that seems to fit the bill: you should cleanly kill (not kill -9 pid, try just kill pid) the corresponding application and it should release that file handle, and the file should be reclaimed.

• however you state that you rebooted: you may have hidden files somewhere underneath your home directory. You could try: find /home/vincent/ -size +1G -ls to get a view of files larger than 1G under /home/vincent directory

• And please note: your invotation with a * of du, ie du ... * will only do du on files that do not start with a . (* will be expanded by your shell to all files and directories that do not start with a .). So it will not run on the "hidden files" of /home/vincent). The printf I give above should ignore this (unless you have specific additionnal rights restrictions on them) and explore both shown and hidden directories and files. You can also re-run the find as root, by pre-pending it with sudo, and see if, when launched as root, it shows more things: sudo find /home/vincent/ -size +1G -ls

• lastly, if you deleted using a recent graphical interface: you may need to empty a "trashcan" to really free the space. (and that trashcan could live underneath your home directory as a ".something" directory, explaining why your home is still as big, and why your du ... * didn't see it)

• If you didn't reboot : You should probably use : lsof -a +L1 can help you find out which deleted (rm'd) files still have opened "file handles" (ie, some program still points to it and thus the file itself is not deleted yet from the filesystem, even though its last name entry has been deleted by rm). The offset will hint at the largest files amongst them. If you see one that seems to fit the bill: you should cleanly kill (not kill -9 pid, try just kill pid) the corresponding application and it should release that file handle, and the file should be reclaimed.

• however you state that you rebooted: you may have hidden files somewhere underneath your home directory. You could try: find /home/vincent/ -size +1G -ls to get a view of files larger than 1G under /home/vincent directory

• And please note: your invotation with a * of du, ie du ... * will only do du on files that do not start with a . (* will be expanded by your shell to all files and directories that do not start with a .). So it will not run on the "hidden files" of /home/vincent). The printf I give above should ignore this (unless you have specific additionnal rights restrictions on them) and explore both shown and hidden directories and files. You can also re-run the find as root, by pre-pending it with sudo, and see if, when launched as root, it shows more things: sudo find /home/vincent/ -size +1G -ls

• lastly, if you deleted using a recent graphical interface: you may need to empty a "trashcan" to really free the space. (and that trashcan could live underneath your home directory as a ".something" directory, explaining why your home is still as big, and why your du ... * didn't see it)