- Status Closed
- Percent Complete
- Task Type Bugs
- Category Drivers
-
Assigned To
zagor - Operating System
- Severity Very Low
- Priority Defer
- Reported Version Release 2.0
- Due in Version Undecided
-
Due Date
Undecided
- Votes
- Private
FS#1285 - Info about free Disk space wrong value
Example (from my Archos Recorder):
Disk space: 18,6 GB occupied: 12,7 GB free: 5,8 GB (from PC Properties)
display of free space in Rockbox 2.0: 15,2 GB
Closed by bagder
2004-03-17 08:19
Reason for closing: Wont Fix
Additional comments about closing:
2004-03-17 08:19
Reason for closing: Wont Fix
Additional comments about closing:
Logged In: YES
user_id=1110
We can't fix problems in
Windows.
Loading...
Available keyboard shortcuts
- Alt + ⇧ Shift + l Login Dialog / Logout
- Alt + ⇧ Shift + a Add new task
- Alt + ⇧ Shift + m My searches
- Alt + ⇧ Shift + t focus taskid search
Tasklist
- o open selected task
- j move cursor down
- k move cursor up
Task Details
- n Next task
- p Previous task
- Alt + ⇧ Shift + e ↵ Enter Edit this task
- Alt + ⇧ Shift + w watch task
- Alt + ⇧ Shift + y Close Task
Task Editing
- Alt + ⇧ Shift + s save task
I also saw this problem on my recorder 20. When attached
to the USB port, windows saw free space as 5gb whereas
the number displayed in the info window was 0.1gb
This problem when away after I wiped, formatted, and
reloaded my disk.
Microsoft Windows does not update the free space information
on the disk according to the filesystem specification.
Therefore Rockbox does not know the amount of free space
without recalculating itself (press play).
AFAIK, this problem does not occur when using Linux to copy
files.
To my knowledge, there is nothing we can do about this until
Microsoft either tells us where they store their free space
information, or they start following their own
specification. I’m not holding my breath for either one…
Your explanation doesn’t fit all the available data; to wit: the
problem was “fixed” on my box when I wiped the disk and
reloaded.
Also, how does this problem affect space allocation for
recording?
This problem does not affect space allocation, only the free space
display. It’s the sum variable that’s wrong, not the block allocation
bitmap.
We can’t fix problems in Windows.