RepoMirrors
/
btrfs-progs
mirror of https://github.com/kdave/btrfs-progs
1
0
Fork 0
Code Issues Packages Projects Releases Wiki Activity

btrfs-progs: docs: fix superscript formatting 

Signed-off-by: David Sterba <dsterba@suse.com>
This commit is contained in:
David Sterba 2022-05-20 23:52:20 +02:00
parent 77ff4d118f
commit 5ba643915c
2 changed files with 4 additions and 4 deletions
Show Stats Download Patch File Download Diff File Expand all files Collapse all files

2
Documentation/Introduction.rst
View File

@ -12,7 +12,7 @@ and easy administration. Its main features and benefits are:
Feature overview:
* Extent based file storage
* 2^64 byte == 16 EiB maximum file size (practical limit is 8 EiB due to Linux VFS)
* 2\ :sup:`64` byte == 16 EiB maximum file size (practical limit is 8 EiB due to Linux VFS)
* Space-efficient packing of small files
* Space-efficient indexed directories
* Dynamic inode allocation

6
Documentation/ch-fs-limits.rst
View File

@ -10,17 +10,17 @@ maximum symlink target length
creation.
maximum number of inodes
2^64^ but depends on the available metadata space as the inodes are created
2\ :sup:`64` but depends on the available metadata space as the inodes are created
dynamically
inode numbers
minimum number: 256 (for subvolumes), regular files and directories: 257
maximum file length
inherent limit of btrfs is 2^64^ (16 EiB) but the linux VFS limit is 2^63^ (8 EiB)
inherent limit of btrfs is 2\ :sup:`64` (16 EiB) but the linux VFS limit is 2\ :sup:`63` (8 EiB)
maximum number of subvolumes
the subvolume ids can go up to 2^64^ but the number of actual subvolumes
the subvolume ids can go up to 2\ :sup:`64` but the number of actual subvolumes
depends on the available metadata space, the space consumed by all subvolume
metadata includes bookkeeping of shared extents can be large (MiB, GiB)