#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):

 Almost a duplicate of #10303.

 Please check the
 [http://wiki.laptop.org/go/Release_notes/10.1.2#Known_Problems Update -
 Known Problems] section of the release notes,
 in particular the linked item that describes [http://wiki.laptop.org/go
 /Olpc-update#Purging_a_previous_OS how to remove the old build].  Doing
 this as part of your customisation may avoid the problem.

 Yes, these 10.1.2 builds are larger than they ever were leading up to
 8.2.1, and so after an olpc-update the total space consumed will tend to
 make "Journal is full" occur more frequently.  How much is too much is a
 matter for debate, and I don't think there is a size goal we are working
 toward.

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