Considerations for FS bounty 3

I was thinking what goes into choosing the disc format for this.

I guess there are some practical considerations like

• How hard it might be to design and implement a new format versus possibly just implementing or even just porting an existing one
• Whether it’s important for users to be able to upgrade their discs ‘in place’ (to take advantage of journalling/metadata) and is there a route from existing FileCore format to new format

and then there are performance considerations like

• What kind of demands does RISC OS and its applications make, and what format serves that well (e.g. patterns of access, numbers/sizes of files etc.)
• Does one format or another work better with the RISC OS environment in terms of when code gets executed (thinking things like background/foreground etc.), memory management, and so on

Plus data recovery. We’d be stuffed without DiscKnight. So a mature format may have better recovery options.

But, on the other hand, what other format can cater for RISC OS metadata such as file types?

I don’t know if the FS needs to remember the position of the binders, but that would answer that question.
https://www.riscosopen.org/forum/forums/5/topics/19513

I use !Links to create links, it works well and is very useful. If this possibility was native in the FS it would allow a better harmonization.

You can store such metadata in extended attributes, and part of bounty #3 is the ability to store arbitrary other data with a file too.

Very much doubt that you’d be able to port data in place from FileCore to any other format.

But bounty #2 doesn’t appear to be making much progress: https://www.riscosopen.org/content/documents/bounties

If you’re considering a new FS format for RISC OS then NTFS is probably worth a look.

A full NTFS implementation would probably be overkill, and you’d probably not want to bother with it’s native wide string support, but as a filesystem it’s quite elegant.

Basically: Everything is a file, a ‘file’ is an entry in the master file table (stored in a file called $MFT). A file is a list of one or more attributes. Attributes can optionally be named. An attribute has a type, an optional name and some data. So a file’s data is stored in an attribute with a ‘DATA’ type. Named ‘DATA’ attributes are used for alternate streams as an example.

Another attribute type is a B*Tree index, with a given name. There’s a specific named one that’s used for directory entries.

A RISC OS implementation wouldn’t need some of the more advanced features (eg, compression), and could ditch the wide chars for filenames. RISC OS file type info would be it’s own attribute.

More info here

While looking to see if NTFS had active patents (doesn’t appear to), I came across this:
https://patents.google.com/patent/CN103218228A/en

Am I missing something? Like, where’s the “invention” here?

Of all the filing systems in the world which you could implement on RISC OS, NTFS would be the very, very last.

It’s vast, horribly inefficient, a memory hog, and took years even with major commercial sponsorship to get it in to the Linux kernel, which now means Microsoft is bound to introduce a breaking change.

There are many, many other truly open filing systems, all on which have plenty of meta data storage for RISC OS filetypes, and including those based on B-Tress and proper snapshot capabilities.

Everybody’s favourite fool ChatGPT suggested:

If patent freedom and full public documentation are critical factors for your use case, EXT4 and Btrfs are the most straightforward options.

Personally, given that most contemporary installations are liable to be using some sort of flash ¹ rather than spinning rust, it would be highly preferable to have a Flash friendly filing system – one that doesn’t cover the device with endless writes to the same places ² and also supports the use of TRIM to allow the device to better manage itself.

¹ SD cards, USB sticks, SSDs, etc.

² https://heyrick.eu/blog/index.php?diary=20240504 – I talk about how my satellite recorder destroys flash media really quickly due to how many writes happen when recording live programming; a cheap little harddisc is much more reliable.

btrfs is the only fs in the last 30 years that has trashed itself for me after a month of use.

Before we can think of using any grown up filing system, we have to implement proper low level disc caching, as the filing system structures are all vastly larger than those used by FileCore, which are small enough to permanently keep in memory. Otherwise you’ll end up with something very slow.

But bounty #2 doesn’t appear to be making much progress: https://www.riscosopen.org/content/documents/bounties

Also annoying is that it all developments (like the bounties here or on the ROD/R-Comp side) happens behind closed doors without any idea of how they go at it. To me the FS bounties look more like trying to patch things together to somewhat handle things it was never designed for.

Personally I’d like to see first drafts APIs to:
- handle 64-bit file sizes
- list/attach/detach devices, partitions, etc.
- easily plugin file system formats (NTFS, EXT4, … ) and let them handle the disc/partition independently of the underlying hardware (ATA/SATA, SCSI, …).

Then, when we have a reasonable, clean, agreed upon API, they can start implementing and choose the preferred file system formats to provide with RISC OS.

we have to implement proper low level disc caching

Yup, and yet…

the filing system structures are all vastly larger than those used by FileCore, which are small enough to permanently keep in memory.

Per bounty 3: “…the map, used to describe where fragments of a file are on the disc, has grown to over 4MB. If we allow many more drives per filing system than the current limit of 8, the computer’s address space will quickly become exhausted”.

So … This kind of smells of “we want this to work on minimal RISC PCs as well as 8GB Pi4s”

the filing system structures are all vastly larger than those used by FileCore, which are small enough to permanently keep in memory.

Per bounty 3: “…the map, used to describe where fragments of a file are on the disc, has grown to over 4MB. If we allow many more drives per filing system than the current limit of 8, the computer’s address space will quickly become exhausted”.

So … This kind of smells of “we want this to work on minimal RISC PCs as well as 8GB Pi4s”

I don’t think you can reliably draw that conclusion from reading that aspect of the bounty. DiscOp64 was expanded to support up to 256 drives per filing system and on my Titanium I have SDFS/SCSIFS/ADFS in regular use, which would be 768 drives with a map of 4MB in current technology → 3GB of address space used on maps.

It’s not talking about amount of RAM being used, because I’d hope that could be dynamically sized or even paged in/out of disc, it’s talking about address space exhaustion which happens just as quickly on an 8MB A7000 as an 8GB Pi 4.

I recently got a confusing “Memory cannot be moved” error when I took an IDE drive out of one computer and put it in an A7000. After a few minutes of headscratching I realised the drive was large enough/had been formatted with a reasonably fine grained LFAU that the map was too big to fit in the RMA. So we already have a situation where some olde computers can’t mount some discs. Maybe any future FileCore extensions would only be enabled if you have > 512MB of RAM or something?

Maybe any future FileCore extensions would only be enabled if you have > 512MB of RAM or something?

Or maybe just better error checking so that it can say something useful here rather than just parroting the error message that the OS provides.

I’m not keen on “if this then that” unless absolutely necessary, because there are always outliers.

I’ll give an example I ran into yesterday. I tried the AI editor that is built into new versions of Google Photos. It refused to touch my photos, claiming that photo spheres and virtual reality photos are not supported.
The truth is that my photos are taken at an aspect something like 21:9 (and frequently composed to fill the frame). It didn’t like that, but was quite happy if I cropped the photo down to 16:9 or 4:3. I sent a bug report but I don’t expect anything to change.

Point is, start making assumptions…..

…better to trap the error when trying to allocate memory and provide a more appropriate message to tell the user that this disc won’t work on this machine because etc etc etc.

the map was too big to fit in the RMA

Aren’t the maps held in DAs that are (specifically inaccessible to user mode code) these days? Or were you using an older RISC OS in the A7000?

Or maybe just better error checking so that it can say something useful here rather than just parroting the error message that the OS provides.

“FileCore in use”?

What about porting ffsv2 from BSD? Or does that not have the necessary metadata support?

(NTFS)

It’s vast, horribly inefficient, a memory hog, and took years even with major commercial sponsorship to get it in to the Linux kernel

Compared to ADFS perhaps?

Modern NTFS is actually pretty decent. It supports ACLs, journalling, TRIM, sparse files, ADS (Alternate Data Stream, kinda like Resource and Data forks on the Mac), compression, encryption, and a whole load of other useful stuff. I don’t tend to get excited about the file system when it ‘just works’. Which, in fairness, modern NTFS does ‘just work’.

MetaData in the FS is an extremely bad idea. It is fragile, non-portable, obscure and unpredictable for users. It is particularly problematic without universal application-implemented support – imagine a task that ‘saves’ a modified file by writing to a temporary file, deleting the original and renaming/copying the temp (eg SparkFS) – this would lose all metadata every single time.

Do not do this.

MetaData in the file however is where the modern world has moved – ISO 26300 and ISO 29500 are both open, patent-unencumbered, zip-based standards that could be easily and transparently supported in RISC OS. By demonstration, ImageFS is a good model (which could be improved upon).

imagine a task that ‘saves’ a modified file by writing to a temporary file, deleting the original and renaming/copying the temp (eg SparkFS) – this would lose all metadata every single time. Do not do this.

Why me 8-) Oh, not me anymore, something ROOL are up to.

One only needs a single pin to pop a balloon. The excellent SparkFS was merely a handy pin.

One only needs a single pin to pop a balloon.

And one mischievous child person :)