Created attachment 675433 [details] screenshot for total size of app. storage Now we get the total size of app. storage by used size + free size. It seems that this would introduce inconsistent value. STR === 1. After flashing, go to Settings app. > Device Storage - Check the total space of application storage 2. Do something to consume the storage space, like go to Gallery app. 3. repeat 1) to check total space Expected: The total space should remain the same. Actual: The total space is changed.
Assignee: nobody → doug.turner
Total space is calculated based on the sum of the "used space" the "free space". As files changes on the /data partition (which they will alot), these two values will change. One approach that df uses is to ceiling the value. This should reduce the amount of turbulence that this number has. Alternatively, we could fix 794397 and provide just the raw size of the partition. Kaze, what do you think?
Milestoning for C2 (deadline of 12/10), as this meets the criteria of "known P2 bugs found before or during C1".
Target Milestone: --- → B2G C2 (20nov-10dec)
I think the only proper fix would be to address bug 794397. This example lets me think that any rounding method will have its glitches regarding to the total space.
Been >2 weeks - any update Doug?
In bug 794397 we say that this bug blocks that one but here we say we should fix that one :) Renomming for discussion at triage.
blocking-basecamp: + → ?
Doug described this is simply a round-off error. I'm marking this as a soft blocker.
blocking-basecamp: ? → -
Priority: P2 → P4
unassigning things that I am not working on.
Firefox OS is not being worked on
Status: NEW → RESOLVED
Last Resolved: 10 months ago
Resolution: --- → WONTFIX
You need to log in before you can comment on or make changes to this bug.