Note: You are viewing an old version of this page. View the current version.

Differences between version 2 and previous revision of sparseify.

Other diffs: Previous Major Revision, Previous Author

Newer page: version 2 Last edited on Tuesday, 8 September 2009 5:25:07 by CyberLeo Revert
Older page: version 1 Last edited on Saturday, 22 August 2009 4:01:37 by CyberLeo Revert
@@ -1,10 +1,14 @@
 Describe [sparseify] here. 
  
-ext2/ext3:  
-http://intgat.tigress.co.uk/rmy/uml/sparsify.html 
+! ext2/ext3  
+* [ http://intgat.tigress.co.uk/rmy/uml/sparsify.html]  
  
-fat12/fat16/fat32:  
+! fat12/fat16/fat32 
  
-ntfs: 
+! ntfs  
+* $Bitmap contains a bitmap covering the entire block device, including metadata and special files.  
+* $MFT contains block size, for computing bitmap offsets. This is usually 4096, for compatibility with stream compression, but it can be different.  
+* ntfsprogs ([http ://www.linux-ntfs.org]) comes in handy: ntfsinfo --mft <dev> for block size, ntfscat <dev> \$Bitmap for bitmap  
+* This has to be the easiest of all, ironically.  
  
-ffs/ufs/ufs2:  
+! ffs/ufs/ufs2 

version 2

Describe sparseify here.

ext2/ext3

fat12/fat16/fat32

ntfs

  • $Bitmap contains a bitmap covering the entire block device, including metadata and special files.
  • $MFT contains block size, for computing bitmap offsets. This is usually 4096, for compatibility with stream compression, but it can be different.
  • ntfsprogs (http://www.linux-ntfs.org) comes in handy: ntfsinfo --mft <dev> for block size, ntfscat <dev> \$Bitmap for bitmap
  • This has to be the easiest of all, ironically.

ffs/ufs/ufs2