#7125 HIGH Never A: Boot fails when disk is full.

[Zarro Boogs per Child]

#7125: Boot fails when disk is full.
---------------------+------------------------------------------------------
  Reporter:  cjb     |       Owner:  cscott        
      Type:  defect  |      Status:  new           
  Priority:  high    |   Milestone:  Never Assigned
 Component:  distro  |     Version:  Update.1      
Resolution:          |    Keywords:                
  Verified:  0       |    Blocking:                
 Blockedby:  5317    |  
---------------------+------------------------------------------------------

Comment(by cscott):

 I agree with bemasc and gnu.  Let's make the system work with 0 available
 space and/or a read-only file system, so that we can use the existing
 sugar tools to clean up.  I don't mind if activity launch fails (which is
 what mstone's second comment is hinting at, I think) as long as it does so
 with a clear message that "the journal is too full, clean up" and that
 that the journal actually starts up properly to allow for the clean up.

 We've got enough time in our current release cycle to fix the actual bug;
 we shouldn't be working on inadequate workarounds at this point.

 As far as mstone's first comment, it seems there are at least two options:
 a) write these files in /tmp or another ramfs, or b) don't (re)write them
 if they've got the same contents as last time.  There may be other
 options.

 The partitioning support will move the /etc/rwtab files to their own
 partition, so using /etc/rwtab will also help ensure space for files
 written during boot.  (http://wiki.laptop.org/go/Early_Boot documents that
 /boot and /security live on the same partition, / lives on another, and
 /home on a third.  /etc/rwtab files live in /security/state.)

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