#6532 BLOC Update1: SD Card Corruption

[Zarro Boogs per Child]

#6532: SD Card Corruption
----------------------+-----------------------------------------------------
  Reporter:  haralds  |       Owner:  dsaxena          
      Type:  defect   |      Status:  assigned         
  Priority:  blocker  |   Milestone:  Update1.1 (8.1.1)
 Component:  kernel   |     Version:                   
Resolution:           |    Keywords:  release?         
  Verified:  0        |    Blocking:  6893             
 Blockedby:           |  
----------------------+-----------------------------------------------------

Comment(by PierreOssman):

 Replying to [comment:23 dsaxena]:
 >
 > Pierre, by "by design", are you referring to the rediscovery of the the
 card as a different block device (as per the fix in #4013) or do you mean
 the data corruption? I don't think the later is really acceptable as
 something for shipping kernels on OLPC or in upstream.

 The different block device name is related, but also different. It is
 caused by something keeping the original device open which prevents the
 new discovery to claim the same name. Instead of disappearing completely,
 it reappears under another name.

 The only safe way of avoiding data corruption is to make sure that you do
 not suspend with dirty filesystems. Either umount them before suspend, or
 fix up the filesystems to do this automatically on suspend (i.e. improve
 the kernel).

 Replying to [comment:24 dsaxena]:
 >
 > CONFIG_UNSAFE_RESUME is disabled on the Ubuntu 2.6.24 kernel and enabled
 on the OLPC 2.6.22 kernel, so it does not seem related to the corruption
 issue.

 The OLPC has a hardware bug that makes the system behave as if
 MMC_UNSAFE_RESUME is always disabled.

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