One of the last updates has this bug. My HDD shows suddenly 0% free space. Then i saved all the data on an external HDD to make my home-partitition empty. Now there are less than 100 MB of data, somewhat between 60-80 MB. The PCManFM-Filemanager shows me now 30.1 GiB of free space.
Created attachment 6907 [details] LXDE-Terminal
Created attachment 6908 [details] PCManFM_Filemanager See the right corner below which shows the Partititions Space
CC: (none) => gerdroscher
This bug is not clear to me. Are you saying PCManFM_Filemanager does not give correct values for total space and free space and that many GBs are "missing"? If so, and if this is about your home directory, then do cd ~ and check with du | awk '/G\t/' whether there are hidden directories that are larger than 1GB if it's about your entire system, then become root su cd / du | awk '/G\t/'
CC: (none) => marja11
The Problem is SOLVED. It was .Synkron which filled my HDD. Many Thanks to Marja :-)
(In reply to Gerd Roscher from comment #4) > The Problem is SOLVED. It was .Synkron which filled my HDD. @ juancho (since you're the only synkron committer, apart from umeabot) Can this bug be closed as invalid, or should Synkron have given a warning before there was 0% space left (see comment #0)
CC: (none) => juan.baptiste
(In reply to Marja van Waes from comment #5) > @ juancho (since you're the only synkron committer, apart from umeabot) > > Can this bug be closed as invalid, or should Synkron have given a warning > before there was 0% space left (see comment #0) Well if synkron should give a warning when running out of space then a bug report should be opened upstream, I think we can close this one as invalid.
(In reply to Juan Luis Baptiste from comment #6) > (In reply to Marja van Waes from comment #5) > > @ juancho (since you're the only synkron committer, apart from umeabot) > > > > Can this bug be closed as invalid, or should Synkron have given a warning > > before there was 0% space left (see comment #0) > > Well if synkron should give a warning when running out of space then a bug > report should be opened upstream, I think we can close this one as invalid. Thanks for the reply :-) So closing.
Status: NEW => RESOLVEDResolution: (none) => INVALID