Opened 6 years ago

Closed 6 years ago

Last modified 21 months ago

#10844 closed enhancement (fixed)

remove unused filesystem blocks from .zd files

Reported by: Quozl Owned by: Quozl
Priority: normal Milestone:
Component: not assigned Version: not specified
Keywords: Cc:
Blocked By: Blocking:
Deployments affected: Action Needed: communicate
Verified: no


As part of #9411 it was requested that "OFW knows to only write blocks/chunks where data actually resides, rather than writing out a full 4gb of data every time".

Since OFW cannot reasonable identify which blocks contain data (requires extensive processing and support for ext2, ext3, and ext4), we instead move this responsibility to olpc-os-builder.

  • fix olpc-os-builder to exclude unused filesystem blocks,
  • fix XO-1.5 OpenFirmware to accept .zd files with missing blocks,
  • fix XO-1.75 OpenFirmware to accept .zd files with missing blocks.

Change History (6)

comment:1 Changed 6 years ago by Quozl

  • Status changed from new to assigned

olpc-os-builder and XO-1.5 OpenFirmware fixed.

comment:2 Changed 6 years ago by dsd

  • Milestone changed from Not Triaged to 1.75-firmware

Just XO-1.75 remaining then?

comment:3 Changed 6 years ago by Quozl

  • Milestone changed from 1.75-firmware to 1.75-software

Works on XO-1.75 A2 now, and a sparse variant of os4 is available for reproducing, assuming you have os4.zd already, and an account on crank, using this quick download method:

cp os4.zd os4-sparse.zd && \
rsync -avP .

What remains is for the XO-1.75 software builds to be sparse.

comment:4 Changed 6 years ago by Quozl

XO-1.75 os9 not sparse. A sparse variant is available:

cp os9.zd os9-sparse.zd && \
rsync -avP .

comment:5 Changed 6 years ago by Quozl

  • Resolution set to fixed
  • Status changed from assigned to closed

Builds for XO-1.75 are sparse, closing this ticket.

comment:6 Changed 21 months ago by Quozl

  • Milestone 1.75-software deleted

Milestone 1.75-software deleted

Note: See TracTickets for help on using tickets.