This morning, I went through analyzing the BFS log area structure. Turns out it’s very different from what I did for our BFS.
Our current log structure looks like this:
block 1 - n:
uint64 number of blocks
off_t array of block numbers
block n+1 - m:
real block data
While the one from BFS looks like this:
uint32 number of runs
uint32 max. number of runs
block_run array of block runs
block 2 - m:
real block data
BFS only has one header block, so it can only store a certain number of blocks per log entry. On the other hand, it uses block runs instead of single block numbers which potentially compacts the size of the block array, but also makes lookups a lot more expensive.
Like a block number, a block run is 8 bytes wide, and is a composed data type that looks like this:
BFS divides the whole volume into allocation groups - each of which can combine up to 65536 blocks. This way, it can also represent a number of sequential blocks. This structure is used a lot throughout BFS, so it’s not surprising to find it again in the log area.
So I will now convert our BFS to use that same format, so that you can safely mount uncleanly unmounted volumes from both operating systems, BeOS and Haiku, and in both directions.
- Haiku Contract Report: September 2021
- Haiku activity report - September 2021
- Haiku activity report - Summer 2021
- GSoC 2021 Final Report: Coding style checker bot for Gerrit
- GSoC 2021 Final Report: Modernizing Chat-O-Matic (Caya)
- GSoC 2021 Improvements to Haiku-format Final update
- Positively Critical: WebPositive and Haiku
- Update #3 from the Promotion Team
- GSOC 2021:Progress Report of Improvements to clang-format
- GSoC 2021 Progress Update 3: Coding style checker bot for Gerrit