#10316 NORM Not Tri: XO-1 "Journal Full" - did 'olpc-update' take too much room in jffs2 ?

[Zarro Boogs per Child]

#10316: XO-1 "Journal Full" - did 'olpc-update' take too much room in jffs2 ?
------------------------------------+---------------------------------------
           Reporter:  mikus         |       Owner:                                   
               Type:  defect        |      Status:  new                              
           Priority:  normal        |   Milestone:  Not Triaged                      
          Component:  not assigned  |     Version:  Development build as of this date
         Resolution:                |    Keywords:                                   
        Next_action:  never set     |    Verified:  0                                
Deployment_affected:                |   Blockedby:                                   
           Blocking:                |  
------------------------------------+---------------------------------------

Comment(by Quozl):

 Since you customise after install, every file you change in the filesystem
 that olpc-update wants to repair will cost toward that 300 MB kept in the
 previous build tree.

 As an example, on an XO-1.5 os851 was installed, olpc-update to os852 was
 done, and the /versions/pristine/ trees for each build showed up with the
 following sizes:

 ||''851''||''852''||''disk free space''||
 ||973 MB||323 MB||1403 MB||

 After removing /versions/pristine/851 the result was:

 ||''851''||''852''||''disk free space''||
 ||not present||973 MB||1433 MB||

 That's a saving of just 30 MB, which also happens to be about the same
 size as the data received by olpc-update as measured by ifconfig.

-- 
Ticket URL: <http://dev.laptop.org/ticket/10316#comment:3>
One Laptop Per Child <http://laptop.org/>
OLPC bug tracking system