https://bugs.kde.org/show_bug.cgi?id=366313
Andrius Štikonas changed:
What|Removed |Added
Status|CONFIRMED |RESOLVED
https://bugs.kde.org/show_bug.cgi?id=366313
Andrius Štikonas changed:
What|Removed |Added
Status|UNCONFIRMED |CONFIRMED
Ever
https://bugs.kde.org/show_bug.cgi?id=366313
--- Comment #7 from Andrius Štikonas ---
Yeah, I'll try to look into it. Now that we know this is caused by dirty bit...
--
You are receiving this mail because:
You are watching all bug changes.
https://bugs.kde.org/show_bug.cgi?id=366313
--- Comment #6 from sascha.zengl...@yahoo.de ---
Done. fsck.msdos shows the correct size even with dirty bit set though. I think
there has to be some condition that decides to not show info if the file system
is corrupt, because if you just took the
https://bugs.kde.org/show_bug.cgi?id=366313
sascha.zengl...@yahoo.de changed:
What|Removed |Added
Severity|normal |wishlist
Summary|Used
https://bugs.kde.org/show_bug.cgi?id=366313
--- Comment #5 from Andrius Štikonas ---
Well, we probably don't want to automatically run fsck that modifies file
system. Maybe it would be nice to show some warning that file system is not
clean. But without looking further into
https://bugs.kde.org/show_bug.cgi?id=366313
--- Comment #4 from sascha.zengl...@yahoo.de ---
I ran the commands and the size was correctly shown.
However, the dirty bit was set. I tried to fix it with fsck.msdos and now the
partition manager shows the correct size - even after restart.
Should I
https://bugs.kde.org/show_bug.cgi?id=366313
--- Comment #3 from Andrius Štikonas ---
Strange, it seems to work for me.
I've just looked at fat code in KPMcore, so used space is calculated by running
fsck.msdos -n -v /dev/sdb2
and looking at cluster size in the output,
https://bugs.kde.org/show_bug.cgi?id=366313
sascha.zengl...@yahoo.de changed:
What|Removed |Added
Summary|Used space is zero if |Used space of Fat32