#10481 NORM Not Tri: Sugar needs to be able to detect errors that occur during file write/copy operations

[Zarro Boogs per Child]

#10481: Sugar needs to be able to detect errors that occur during file write/copy
operations
-----------------------+----------------------------------------------------
 Reporter:  greenfeld  |                 Owner:  erikos                            
     Type:  defect     |                Status:  new                               
 Priority:  normal     |             Milestone:  Not Triaged                       
Component:  sugar      |               Version:  Development source as of this date
 Keywords:             |           Next_action:  diagnose                          
 Verified:  0          |   Deployment_affected:                                    
Blockedby:             |              Blocking:                                    
-----------------------+----------------------------------------------------
 The Journal (and ideally all of Sugar) should be able to catch if a write
 fails while copying/duplicating an object due to running out of available
 disk space on the target media.  In an ideal world, we also would check
 the file size against the available disk space before copying and not
 attempt a copy/write operation if there is not enough (although this may
 fail both ways for compressible filesystems like that on an XO-1).

 Right now we can only detect if we lack the permissions to write the file
 before the file operation starts.  We should be able to catch errors that
 occur during the file writing/copying process, notify the user, and be
 able to recover from them gracefully.

 Seen in 10.1.3 os354 & prior.

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