#7125 BLOC 8.2.0 (: Boot fails when disk is full (tracker bug) (was: Boot fails when disk is full.)

[Zarro Boogs per Child]

#7125: Boot fails when disk is full (tracker bug)
--------------------------------------------------------+-------------------
   Reporter:  cjb                                       |       Owner:  cscott              
       Type:  defect                                    |      Status:  new                 
   Priority:  blocker                                   |   Milestone:  8.2.0 (was Update.2)
  Component:  distro                                    |     Version:  Update.1            
 Resolution:                                            |    Keywords:  blocks:8.2.0        
Next_action:  design                                    |    Verified:  0                   
  Blockedby:  5317, 7586, 7587, 7588, 7589, 7590, 7591  |    Blocking:                      
--------------------------------------------------------+-------------------
Changes (by cscott):

  * blockedby:  5317 => 5317, 7586, 7587, 7588, 7589, 7590, 7591


Old description:

> We're probably going to see this a lot in the field.  It might be worth
> having some recovery logic.  Here's a straw-man:  if disk is full at
> boot, delete the single largest journal entry, iterate until disk is not
> full anymore.

New description:

 We're probably going to see this a lot in the field.  It might be worth
 having some recovery logic.

 (This bug has become a tracker bug for related issues.  cjb's original
 proposal has moved to #7591.)

--

Comment:

 Here's a list of tasks associated with this general bug, and trac #s  for
 them:
  * the initscripts should be sure to unfreeze the dcon if/when X fails to
 start.  This ensures that the system is obviously recoverable (you can
 recover by rebooting with the check key held down, but this is not
 obvious!). (#7586)
  * sugar should, ideally, start even if flash is full.   It is currently
 failing when writing to ~olpc/.boot_time or some such, and crashing.
 (#7587)
  * once sugar starts, there should be a message indicating that the NAND
 is critically full. (#7588)
  * trying to save new content to the journal should also give an obvious
 message that the NAND is full. (#7589)
  * removing content from the journal should work even if NAND is full.
 (#7590)
  * automatically remove content from the journal is NAND is full?
 (controversial) (#7591)
  * Jffs2 is slow when it fills/root should have reserved space (#5317)

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