Jump to content

Block allocation map

From Wikipedia, the free encyclopedia
This is an old revision of this page, as edited by Hydradix (talk | contribs) at 20:07, 5 February 2013 (add reference for sparse files; added detriment of allocation method with reference). The present address (URL) is a permanent link to this revision, which may differ significantly from the current revision.

CP/M used a block allocation map in its directory. Each directory entry could list 8 or 16 blocks (depending on disk format) that were allocated to a file. If a file used more blocks, additional directory entries would be needed. Thus, a single file could have multiple directory entries. A benefit of this method is the possibility to use sparse files by declaring a large file size but only allocating blocks that are actually used.[1] A detriment of this method is the disk may have free space (unallocated blocks) but data cannot be appended to a file because all directory entries are used.[2]

Errata

The Commodore DOS used a similarly named but significantly different Block availability map.

See also

References

  1. ^ CP/M Plus Operating System Programmer's Guide (Second ed.). Monterey, CA: Digital Research, Inc. 1983. p. 2-12.
  2. ^ CP/M Plus Operating System Programmer's Guide (Second ed.). Monterey, CA: Digital Research, Inc. 1983. p. 3-51.