Arrgh, IBrowse got me again!

[MikeB]

@lempkee

I agree, PFS3 is great and it is 100% compatible.
Plus it has direct scsi support.

But if it comes down to facts well:

1. 500% faster read/writes and scanning directories. The performance gain varies with depending on devices, buffers and processor but gains of upto 500% are no exception.

2.Disks are always valid, no matter what happens, its called Atomic Commit. More info in PFS3 Docs.

3. Reliability - very reliable and stable filesystem. Has built in problem detection mechanism. When PFS3 detects a problem it will do everything it can to save your data (see problem detection)

4. Parralel access without performance loss.
FFS breaks down when you try to do several things simultaneously on one volume. PFS3 does not!.

5. Full Compatibility.
PFS3 is fully compatible with FFS at filesystem level, but for a few rarely used filesystem packets. What this means is that practically all tools and applications that use the filesystem to access the disk work. All normal applications do this, including most backup tools.
Some applications, however, access the disk directly, bypassing the filesystem.  Such applications won't work if they expect a FFS disk. Examples are disk optimisers and repair tools (like Quarterback Tools and DiskSalv).
Such tools have to be specially made or adapted in order to function with PFS3. The reason those tools don't work is that PFS3 stores
information differently on the disk than FFS does. In fact, PFS3 does this in a more efficient and reliable way.
The only feature of FFS that is not supported by PFS3 are record locks. Not a single application that uses this FFS feature is known to us.

6. Easy Filerecovery - lost files can be restored from the delete directory. This includes overwritten files.

7. Long filename support - supports 107 characters

8. Automatically truncated logfiles - stopping them from growing indefinitely.

9. Large disk support - pfs3 supports disk and partitions of upto 104GB using the direct scsi and TD64 interfaces.

10. Multiuser support - a multi user system turns PFS3 into a MuFS replacement. It adds user based access rights to the files on the disk. Each file and directory can be assigned to specific users and user groups. The owner of a file can determine who may have access the file.

The ONLY issue i have had with PFS3 is if you dont follow the advice in the documentation and set the incorrect mask values and pfs3 driver, then your get problems on the disk.
But even this is recoverable to another partition as long as you act quickly rather than leaving it for weeks.

[MikeB]

@jetracer

All your comments are no reason to say don't buy PFS3.
I've tested SFS on an Amiga A4000T with Cyberstorm SCSI Drive, it is slower than PFS3.
SFS is free but its beta!!!!
Plus the other reasons for not using SFS until its out of BETA stage are listed in their own documentation.  

People have a choice, and i'm not saying SFS is crap i'm saying its BETA stage. Do you really want people to store their only data on a beta filesystem??
You added comments about "DO NOT SPEND MONEY ON PFS3!", one big issue i have is if more Amiga users spend money on good software maybe developers would stay around.
The only comment i have for you is don't write stuff unless you know all the facts.


---------------------
There are a number of things you should know before using this
filesystem.

 - Do not use disk caching software which delays writes on a SFS disk.
   PowerCache is known to have this feature (but it can be disabled).
   SFS relies on data being written in a special order to the disk so
   it can keep your disk valid it all times.  Caching software which
   delays those writes can therefore interfere with this process.

 - Programs using ixemul (GNU C for example) might have problems with
   this filesystem as well, although this is unlikely.

 - Disk changes are implemented, but haven't been fully tested so you
   might experience problems.  The c:DiskChange command might help to
   avoid some problems by telling the filesystem explicitely that the
   disk has changed.

 - The filesystem doesn't pay attention to write-protection (the
   filesystem will get confused eventually if you've write protected
   the disk and start writing data to it).

 - Not all space gets freed again if you delete all files from a disk.
   This is caused by the fact that the filesystem allocates parts of
   the disk to store its administration blocks on demand.  These areas
   aren't freed again (but they are reused if needed!).  This will be
   fixed eventually, but is no more than a minor inconvience at the
   moment.

 - The filesystem puts up requesters during booting to inform you that
   last changes to the disk before the last reset weren't completed
   yet.  This means booting may be interrupted and you'll have to
   confirm the requesters first.

 - Although the filesystem supports blocksizes upto 32 kB, it is not
   recommended to use such large blocksizes.  SFS performs very well
   with small blocksizes and gains very little or even loses speed
   with larger blocksizes.  I'd recommend not using blocksizes larger
   than 2 kB.

 - The structure of future versions of this filesystem WILL change
   without being backwards compatible as long as the filesytem is in
   BETA stage.  This means you will need to reformat any SFS
   partitions you have before being able to use a new version.  Check
   the history to see whether or not you need to reformat your disk.

Don't forget this filesystem is BETA - this means it might crash your
machine and damage the files you stored with it.  Use it at your own
risk and always keep backups of your important data (but that goes
without saying anyway).