#10079 NORM Not Tri: olpc-update of 2g machine fails, causes disk-full on next boot

[Zarro Boogs per Child]

#10079: olpc-update of 2g machine fails, causes disk-full on next boot
------------------------------------+---------------------------------------
           Reporter:  pgf           |       Owner:               
               Type:  defect        |      Status:  new          
           Priority:  normal        |   Milestone:  Not Triaged  
          Component:  not assigned  |     Version:  not specified
         Resolution:                |    Keywords:               
        Next_action:  never set     |    Verified:  0            
Deployment_affected:                |   Blockedby:               
           Blocking:                |  
------------------------------------+---------------------------------------

Comment(by pgf):

 Replying to [comment:1 Quozl]:
 > agreed, removing a failed update might be useful, but this prevents
 eventual gradual use of olpc-update; a laptop that had insufficient space
 for the update would repeatedly download and then have the downloaded data
 destroyed.
 >

 we're talking about a case where the failed update is preventing the
 machine from booting.  there's no way that update will ever finish, or
 succeed (there's presumably no room), so the only reasonable thing to do
 is remove it.

 agreed that preventing the update attempt if there's not enough space
 would be good too, but i don't know whether we can know easily how much
 space any given update will take, since it depends on how much the update
 has in common with the current running image.

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