[LUDOC-159] Provide more details of "extents" (Glossary) Created: 14/Jun/13  Updated: 26/Aug/13  Resolved: 26/Aug/13

Status: Resolved
Project: Lustre Documentation
Component/s: None
Affects Version/s: None
Fix Version/s: None

Type: Improvement Priority: Minor
Reporter: Brett Lee (Inactive) Assignee: Linda Bebernes (Inactive)
Resolution: Fixed Votes: 0
Labels: QContent

Business Value: 4.26
Rank (Obsolete): 8708

 Description   

The term "extents" is used but never defined.



 Comments   
Comment by Linda Bebernes (Inactive) [ 20/Jun/13 ]

Definition from wikipedia

Extents (ext4)
Extents replace the traditional block mapping scheme used by ext2 and ext3. An extent is a range of contiguous physical blocks, improving large file performance and reducing fragmentation. A single extent in ext4 can map up to 128 MiB of contiguous space with a 4 KiB block size.[1] There can be four extents stored in the inode. When there are more than four extents to a file, the rest of the extents are indexed in an Htree.

In what context are extents relevant to a Lustre user? Would it be sufficient to add more explanatory text to the section 31.2.3 and 31.2.5 and possibly also Sections 32.4.2 and 32.4.3? Other places "extents" is mentioned in the manual aside from code examples are 8.1.1.2 and 36.19.2.
When did Lustre start supporting this feature?

Comment by Linda Bebernes (Inactive) [ 25/Jun/13 ]

Extents are mentioned in these sections in the manual:
8.1.1.2 (installing e2fsprogs)
31.2.3 - table
31.2.5
31.2.10 - table
32.4.2
32.4.3
36.19.2

Comment by Linda Bebernes (Inactive) [ 27/Jun/13 ]

Best solution may be to add a definition of extents to the glossary similar to:
"similar in function to the block mappings in an ext3 inode, an extent is a range of contiguous physical blocks that are mapped via an ext4 inode."

Comment by Linda Bebernes (Inactive) [ 15/Jul/13 ]

A definition of extents has been added to the glossary and is now ready for review at http://review.whamcloud.com/#/c/6990/

Comment by Linda Bebernes (Inactive) [ 26/Aug/13 ]

Changes merged

Generated at Sat Feb 10 03:40:42 UTC 2024 using Jira 9.4.14#940014-sha1:734e6822bbf0d45eff9af51f82432957f73aa32c.