@buzz
Funny that, since I've used PFS3 in Enforcer, CyberGuard and MorphOS (which has built-in enforcer like environment) for years, and it never has hit, not even once.
I've used it with Commodore scsi.device (A1200 IDE), Phase5 blizzppc.device (BPPC SCSI-2) and MorphOS ide.device (UDMA IDE).
PFS3 has an annoying thing where it has a delay before updating some information after a write, so if you edit a file in ced and save and reboot too quickly you loose your changes.
True, but this speeds up disk writes massively. Also, the data is written to disk in a way that the disk can never become corrupt. The worst that can happen is that you just lose the last changes to the filesystem. And, if you send ACTION_FLUSH packet to the filesystem it will sync the uncommited buffer contents to disk right away (quite useful to have in reboot tool).
I did have pfs3 partitions go NONDOS on me a couple of times too. The pfs doctor tool was useless.
The few times I had problems due to trying write cache (bad idea with filesystem that depends on consistent disk write order), pfsdoctor recovered everything just fine.
Maybe I've just been lucky for the last ~10 years, but I've never had major problems (data lossage) with PFS, AFS, PFS2 or PFS3.
SFS on the other hand completely nuked after copying 20GB data on a freshly formatted partition. That was enough SFS for me.
