This is a bug in SFS, and one of the reasons why I am so skeptical about third party file systems. The best workaround: Don't use SFS. Is it still supported to get the bug fixed? No.
From a purely technical perspective: SFS fills info->id_DiskState with the partition identifier (SFS\0) instead of the disk state (which should be DOS\0 for a validated disk), and hence workbench is confused. The matter is subtle, and it is easy to confuse one with the other, even more so since the same happened in the FFS which - again by a historical accident - uses DOS\n (n=0...
instead of DOS\0 for the disk state. Other tools will be confused by this as well.
Wahoo, what a quick reply! Thanks!


Thanks for the technical explanation as well.
My aim was to speed up file operations and boot time on the cosy A1200 a bit.
Although your hint about third party FileSystems, I'll give PFS3 a shot and report here for completeness.
If it does have some quirks too, I'll revert back to FFS; but as I'm at it, to the latest version (should be 45.16 AFAIK).
FastFileSystem has served well for the last 2 decades anyway..

Amigo1