mirror of
git://git.kernel.org/pub/scm/linux/kernel/git/torvalds/linux.git
synced 2025-08-05 16:54:27 +00:00

The short description of inode table is in bitmaps.rst alongside the proper bitmpas documentation. The docs file is short enough that it fits whole browser screen on desktop, which implies that when readers click "Inode Table", they will essentially see bitmaps docs. Move inode table short description. Signed-off-by: Bagas Sanjaya <bagasdotme@gmail.com> Acked-by: Theodore Ts'o <tytso@mit.edu> Acked-by: Darrick J. Wong <djwong@kernel.org> Signed-off-by: Jonathan Corbet <corbet@lwn.net> Link: https://lore.kernel.org/r/20250620105643.25141-7-bagasdotme@gmail.com
21 lines
871 B
ReStructuredText
21 lines
871 B
ReStructuredText
.. SPDX-License-Identifier: GPL-2.0
|
|
|
|
Block and inode Bitmaps
|
|
-----------------------
|
|
|
|
The data block bitmap tracks the usage of data blocks within the block
|
|
group.
|
|
|
|
The inode bitmap records which entries in the inode table are in use.
|
|
|
|
As with most bitmaps, one bit represents the usage status of one data
|
|
block or inode table entry. This implies a block group size of 8 *
|
|
number_of_bytes_in_a_logical_block.
|
|
|
|
NOTE: If ``BLOCK_UNINIT`` is set for a given block group, various parts
|
|
of the kernel and e2fsprogs code pretends that the block bitmap contains
|
|
zeros (i.e. all blocks in the group are free). However, it is not
|
|
necessarily the case that no blocks are in use -- if ``meta_bg`` is set,
|
|
the bitmaps and group descriptor live inside the group. Unfortunately,
|
|
ext2fs_test_block_bitmap2() will return '0' for those locations,
|
|
which produces confusing debugfs output.
|