Matches in DBpedia 2015-10 for { ?s ?p "An extent is a contiguous area of storage reserved for a file in a file system, represented as a range. A file can consist of zero or more extents; one file fragment requires one extent. The direct benefit is in storing each range compactly as two numbers, instead of canonically storing every block number in the range.Extent-based file systems can also eliminate most of the metadata overhead of large files that would traditionally be taken up by the block allocation tree. Because the savings are small compared to the amount of stored data (for all file sizes in general) but make up a large portion of the metadata (for large files), the benefits in storage efficiency and performance are slight, whereas the reduction in metadata is significant and reduces exposure to file system corruption as one bad sector in the block allocation tree causes much greater data loss than one bad sector in stored data.In order to resist fragmentation, several extent based file systems do allocate-on-flush. Many modern fault tolerant file systems also do copy-on-write, although that increases fragmentation. As a similar design, the CP/M file system uses extents as well, but those do not correspond to the definition given above. CP/M's extents appear contiguously as a single block in the combined directory/allocation table, and they do not necessarily correspond to a contiguous data area on disk."@en }
Showing triples 1 to 1 of
1
with 100 triples per page.
- Extent_(file_systems) abstract "An extent is a contiguous area of storage reserved for a file in a file system, represented as a range. A file can consist of zero or more extents; one file fragment requires one extent. The direct benefit is in storing each range compactly as two numbers, instead of canonically storing every block number in the range.Extent-based file systems can also eliminate most of the metadata overhead of large files that would traditionally be taken up by the block allocation tree. Because the savings are small compared to the amount of stored data (for all file sizes in general) but make up a large portion of the metadata (for large files), the benefits in storage efficiency and performance are slight, whereas the reduction in metadata is significant and reduces exposure to file system corruption as one bad sector in the block allocation tree causes much greater data loss than one bad sector in stored data.In order to resist fragmentation, several extent based file systems do allocate-on-flush. Many modern fault tolerant file systems also do copy-on-write, although that increases fragmentation. As a similar design, the CP/M file system uses extents as well, but those do not correspond to the definition given above. CP/M's extents appear contiguously as a single block in the combined directory/allocation table, and they do not necessarily correspond to a contiguous data area on disk.".