Editing Ploop/format
Warning: You are not logged in. Your IP address will be publicly visible if you make any edits. If you log in or create an account, your edits will be attributed to your username, along with other benefits.
The edit can be undone.
Please check the comparison below to verify that this is what you want to do, and then save the changes below to finish undoing the edit.
| Latest revision | Your text | ||
| Line 1: | Line 1: | ||
| − | |||
| − | |||
A ploop image file format is pretty simple. | A ploop image file format is pretty simple. | ||
| − | |||
* Image consists of cluster blocks (default cluster block size is 1 MB). | * Image consists of cluster blocks (default cluster block size is 1 MB). | ||
* First there are some cluster blocks with BAT (Block Allocation Table), then there are some cluster blocks with data. | * First there are some cluster blocks with BAT (Block Allocation Table), then there are some cluster blocks with data. | ||
| Line 10: | Line 7: | ||
* If a slot N contains value M, then a request to a cluster-block N of a /dev/ploopXXX device is redirected to a cluster-block M in an image file. N is counted from 0, while M is counted from 1 (0 means block is not yet allocated). | * If a slot N contains value M, then a request to a cluster-block N of a /dev/ploopXXX device is redirected to a cluster-block M in an image file. N is counted from 0, while M is counted from 1 (0 means block is not yet allocated). | ||
| − | |||
For the rest of the story, see sources. | For the rest of the story, see sources. | ||
| − | |||
[[Category: Storage]] | [[Category: Storage]] | ||
