#10040 HIGH 1.5-sof: OFW unable to burn 4GB image onto 4GB SD card

[Zarro Boogs per Child]

#10040: OFW unable to burn 4GB image onto 4GB SD card
------------------------------------+---------------------------------------
           Reporter:  wad           |       Owner:  cjb                              
               Type:  defect        |      Status:  new                              
           Priority:  high          |   Milestone:  1.5-software-update              
          Component:  build-system  |     Version:  Development build as of this date
         Resolution:                |    Keywords:                                   
        Next_action:  diagnose      |    Verified:  0                                
Deployment_affected:                |   Blockedby:                                   
           Blocking:                |  
------------------------------------+---------------------------------------

Comment(by pgf):

 i just timed the expansion of our 2g (201) image to fit my 4g card.  it
 took 38.4 seconds, real-time.  the filesystem was unmounted, and i was
 running from a rootfs on a USB stick.  although the resize2fs man page
 claims to be able to resize mounted filesystems, it got EBUSY when trying
 to open /dev/mmcblk0p2 when that was the root fs.  (we could get around
 this by running resize2fs in the initramfs before the mount.)

 i think 38 seconds is too long to delay the first boot.  however, this
 technique might still be useful if we continued building two images:  one
 of them 1.6G, the other 3.6G (for example).

 this would be a good way to get full use of bigger cards.   the Adata card
 has a device capacity of 7698432 512-byte blocks.  by comparison, the card
 in my C1 has 7954432.  that's over 3% smaller.

 but we need to think about whether the risk of a power cycle, if resize2fs
 is unsafe in that regard (likely), makes it worth it.

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