cloop

<h2 id="design">Design</h2>
<p>cloop images contain:
</p>
<ul><li>A <a href="/facts/Shell_script/NE7YvsBD">shell script</a> (with mount commands for the image)</li>
<li>A header with the number of blocks and the uncompressed block size</li>
<li>A seek index with compressed and uncompressed block sizes in pairs</li>
<li><a href="/facts/Zlib/rExIchaK">zlib</a>-compressed data blocks, packed end-to-end</li></ul>
<p>The data blocks are compressed separately; this makes it possible to seek to individual blocks without having to decompress the entire image from the start, but at the cost of slightly reducing the compression ratio.  Live CD images typically use a block size of 256 KB as a compromise between decompression speed and space-efficiency.
</p><p>Apple uses a similar file format in the compressed variant of its <a href="/facts/.dmg/v7r8Uakn">DMG</a> disk images.
</p>
<h2 id="limitations">Limitations</h2>
<p>The design of the cloop driver requires that compressed blocks be read whole from disk.  This makes cloop access inherently slower when there are many scattered reads, which can happen if the system is low on memory or when a large program with many shared libraries is starting. A big issue is the seek time for CD-ROM drives (~80 ms), which exceeds that of hard disks (~10 ms) by a large factor. On the other hand, because files are packed together, reading a compressed block may thus bring in more than one file into the cache. The effects of tail packing are known to improve seek times (cf. <a href="/facts/Reiserfs/aGg9PTtk">reiserfs</a>, <a href="/facts/Btrfs/lPwmXVJ6">btrfs</a>), especially for small files. Some performance tests related to cloop have been conducted.<a class="footnote-ref" id="fnref:1" href="#fn:1"><sup>1</sup></a>
</p>
<h2 id="see-also">See also</h2>
<ul><li><a href="/facts/Loop_device/tYrnMSWm">Loop device</a></li>
<li><a href="/facts/Cramfs/j0r9BsBp">Cramfs</a></li>
<li><a href="/facts/SquashFS/shx5yhCv">SquashFS</a></li>
<li><a href="/facts/E2compr/ftyVw4Kv">e2compr</a></li></ul>

<h2 id="external-links">External links</h2>

Look up <i>cloop</i> in Wiktionary, the free dictionary.

<ul><li>cloop <a href="https://web.archive.org/web/20120501230646/http://debian-knoppix.alioth.debian.org/packages/cloop/">sources</a> against the mainline Linux kernels and a <a href="http://hg.slitaz.org/wok/raw-file/tip/linux-cloop/stuff/cloop.u">patch</a> to support any known cloop format. Note: versions 0.xx are for kernel 2.2; 1.xx are for kernel 2.4; 2.xx are for kernel 2.4 and 2.6.</li>
<li><a href="http://www.knoppix.net/wiki/Cloop">cloop at Knoppix Linux Wiki</a> (installation instructions are here)</li>
<li>Slides from a LinuxTag <a href="http://www.knopper.net/knoppix-info/cloop-chlt4-screen.pdf">presentation</a> by Klaus Knopper on the implementation of cloop (in German).</li>
<li>A <a href="http://fusecloop.sourceforge.net/">fuse</a> driver for cloop with a <a href="http://hg.slitaz.org/wok/raw-file/tip/fusecloop/stuff/fusecloop.u">patch</a> (<a href="http://hg.slitaz.org/wok/file/tip/fusecloop/description.txt#l1">description</a>) to support any known cloop format and the <a href="http://cook.slitaz.org/cooker.cgi?download=../wok/fusecloop/taz/fusecloop-0.20.1/fs/usr/bin/fusecloop">binary</a>.</li></ul>

<h2 id="references">References</h2>

<ol>
<li id="fn:1"><p>Cloop performance testing on a ThinkPad T61[dead link‍] 31-Dec-2011 <a href="http://www-etud.iro.umontreal.ca/~jaegerch/div/cloop_performance_tests" target="_blank">http://www-etud.iro.umontreal.ca/~jaegerch/div/cloop_performance_tests</a> <a href="#fnref:1" class="footnote-back-ref">↩</a></p></li>
</ol>

cloop open-in-new

cloop