Smart Filesystem 1.205 - amiga-news.de Forum

amiga-news.de Forum > Amiga, AmigaOS 4 > Smart Filesystem 1.205

[ - Search - New posts - Register - Login - ]

-1-

[ - Post reply - ]

2003-05-06, 07:20 h

The_Killer
Posts: 216
User

Hallo !

In den neuen Aminet Uploads vom 05.05.03 ist die neue Version 1.205 des Smart Filesystems zu finden.

Hat die schon jemand getestet ?

Hier nochmal der Auszug der beiliegenden Readme.

Short: Smart Filesystem copyrighted by John Hendrikx
Author: hjohn@xs4all.nl
Uploader: PIK@amigo.ping.de
Version: 1.205
Type: disk/misc
Replaces: disk/misc/SFS.lha
Requires: 68020 or better, AmigaOS 3.0 or better

------------------------------------------------------------
This filesystem is BETA -- this means it is not finished.

USE AT YOUR OWN RISK!
------------------------------------------------------------

For more information read the included documentation

Introduction
------------

Smart Filesystem is a new filesystem for your Amiga.
A filesystem's main purpose is to store files on a disk in
such a way that they can be located and used quickly. How
this is done is up to the filesystem. The way information
is stored on your disk has a large impact on speed and space
efficiency, and so these factors can vary a lot from
filesystem to filesystem.

Smart Filesystem was created to provide you with an
alternative to the Fast Fileystem. Smart Filesystem makes
more efficient use of your disk space (max speed with
512 bytes/block!), has better performance in most areas and
will allow for new features never seen before in an Amiga
filesystem.

Features
--------
o FAST seeking. Even in extremely large files.

o FAST reading of directories.

o FAST defragmentation routines (built-in optimiser)

o Disk space is used VERY efficiently.

o Blocksizes of 512 bytes up to 32768 bytes are supported.
(512 BYTES FOR BEST PERFORMANCE)

o The length of file and dir names can be 107 characters. The lenght
of 'pathes' can be 255 characters (AmigaDOS, see changes?!)

o Volumename can be 30 characters (AmigaDOS)

o The size of a file is limited to 2 GB (AmigaDOS)

o The length of comments can be 79 characters (like FFS)

o Support for partitions larger than 4 GB or located (/partially)
beyond the 4 GB barrier on your drive. There is support for the
New Style Devices (NSD) and the 64-bit trackdisk commands (TD64)
which support 64 bit access.

o Supports large partitions. The limit is about 2 TB, but it can be
more depending on the blocksize (32KB/Block -> 128 TB). Yes! ;-)

o Modifying data on your disk is very safe. Even if your system is
resetted, crashes or suffers from powerloss your disk will not be
corrupted and will not require long validation procedures before
you will be able to use it again. In the worst case you will
only lose the last few modifications made to the disk.

o There is a built-in configurable read-ahead cache system which
tries to speed up small disk accesses. This cache has as a
primary purpose to speed up directory reading but also works very
well to speed up files read by applications which use small
buffers.

o Supports Notification and ExamineAll.

o Supports softlinks (hardlinks are not supported for now).

o Using the SFSformat command you can format your SFS partition with
case sensitive file and directory names. Default is case insensitive
(like FFS).

o There is a special directory which contains the last few files
which were deleted. (see sfsformat.txt)

To do
-----

o Make sure that freeing an adminspace area cannot get
overwritten by data or a new adminspace container in the same
Transaction (currently this cannot occur as adminspace areas
are not freed).

o Node system doesn't really need the Parent pointers in their
blocks. Removing them will give extra room in the Node
blocks, but will also make moving Node blocks easier.
[Note: The old node system is likely to be removed completely
in favor of the new B+-Tree system]

o Links.

o Small files (less than blocksize) can be accessed directly without
going through the B-Tree, since the file-header contains a pointer
to the first block. Also, we might be able to keep additional
information in the fileheader, as any changes to the Extents will
most likely also result in a change in the file header...

Unimplemented packets
---------------------

ACTION_LOCK_RECORD
ACTION_FREE_RECORD
ACTION_MAKE_LINK (soft links only at the moment)

KNOWN BUGS
----------

o 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.

CU

The_Killer