Hi, I was thinking about using a raw or cooked partition for storing blocks of data and I wanted to write this in Rust. Essentially writing a file system.
Wanted to pick some brains on some of the higher level design issues....
#Writing a persistence layer in Rust
onyx girder
rancid mulch
Hi, I was thinking about using a raw or cooked partition for storing blocks of d...
Do you have any specific issue you want to talk about? Most of us are probably not familiar with filesystems: we can likely help you with most problems you may encounter, but can't guess what those problems would be
ionic vector
Hi, I was thinking about using a raw or cooked partition for storing blocks of d...
so on linux you can just open a partition with /dev/sdxy or like /dev/nvmexnypz or something
onyx girder
Hi, so there two different sets of issues.
High level design and design considerations...
Then issues w implementation in Rust. (Best way to do it)
In terms of this... The idea at a high level is to take ownership of the device.
(Or cooked chunks...) and then lay out the data within it.
So I imagine I would store data in blocks (size would have to be preset to something like 4mb ... and then I would have to have a way to manage the list of blocks available, and in use. Then when the data blocks are used for something like a file or an object store , or as a segment of a stream.
In terms of streams, I'd have to manage the streams... then for each stream, the topic and then the blocks associated with it. (And even here there's a question do I manage the data blocks per stream or per topic...)