#10303 HIGH Not Tri: XO-1 Persistent "Journal Full" message on build 850

[Zarro Boogs per Child]

#10303: XO-1 Persistent "Journal Full" message on build 850
---------------------------------------+------------------------------------
           Reporter:  maraschino       |       Owner:  dsd          
               Type:  defect           |      Status:  new          
           Priority:  high             |   Milestone:  Not Triaged  
          Component:  sugar-datastore  |     Version:  not specified
         Resolution:                   |    Keywords:  journal full 
        Next_action:  test in build    |    Verified:  0            
Deployment_affected:                   |   Blockedby:               
           Blocking:                   |  
---------------------------------------+------------------------------------

Comment(by Quozl):

 Technical investigation.

 "Your Journal is full" is intended to appear if the available space on the
 profile path is below 50MB.  The profile path is normally
 /home/olpc/.sugar/default.  The relevant function is
 _check_available_space in journalactivity.py and it calls os.statvfs,
 calculates the free space in bytes, and if it is less than 52428800 bytes
 activates the message.

 This method of testing available space verifies fine on XO-1 os851 on a
 test system here.

 Once the message appears, if it is dismissed (by clicking on the Show
 Journal button) then on next update to the Journal if the triggering
 condition persists the message will reappear.  The persistent nature of
 the message is a known problem (SL 630 SL 172).

 A right-click on the Journal icon in the Home View displays the fraction
 of free space relative to total space, with a label describing the free
 space in megabytes.  This is implemented in JournalPalette.*popup_cb() in
 palettes.py.  It uses the same method of calculating free space as the
 journal full message does.  So a displayed free space of 60MB should
 represent an amount greater than the 50MB trigger amount.

 Activity startup may consume some space, but it is unlikely to consume
 10Mb.

 Removal of journal entries with ''rm -r'' may not effectively clear space
 since the datastore process is now a separate process with this version of
 Sugar; it keeps several files open.  A restart of Sugar starts a new
 datastore process.

 Related bugs:
  * [http://bugs.sugarlabs.org/ticket/172 SL #172] (Difficult to fix a
 journal filled by downloading)
  * [http://bugs.sugarlabs.org/ticket/394 SL #394] (cancel a download if
 space is very tight)
  * [http://bugs.sugarlabs.org/ticket/630 SL #630] (Journal full message
 has issues)

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