AFS FAQ
Table of contents - Common Questions
![]()
pfs95.lha disk/misc 232K Professional file system for the Amiga
In an interesting turn of events Michiel Pelt, the author of AFS, posted the AFS disk structure to the AFS mailing list. To read this message follow this link...
This information can be used to manually repair an AFS partition.
![]()
![]()
![]()
To undelete a file simply copy it from the :.deldir directory and correct the protection bits. It is a BAD idea to copy the file to the same partition as this may use the space of the file you are recovering which WILL result in a corrupt file.
Note that you cannot rename files from the :.deldir directory.
Guy Baltet has written a program to automate this process with a nice MUI GUI interface. It is available from AmiNet :-
disk/misc/AFSUndelete1.5.lha
Please do not ask FLD for support for this program.
![]()
Using a program call 'MakeRollOver' you can create a new logfile. When it is created you should choose how many disks blocks you wish to allocate to the logfile. This space is allocated immediately although the size will show as 0. As data is appended to the file it will grow in size until it reaches the size you allocated. After this point data will still be appended to the end of logfile, but the file will not get any bigger. This is achieved by AFS removing the oldest entries from the start of the file.
Note that when you create a rollover file you specify the number of blocks to allocate. Not the number of bytes !
Note also that rollover files are converted to normal files by all known backup systems. If you ever have to restore you will have to rename the file, create the rollover version and copy the data back into it. Remember to delete the temporary copy !
![]()
It is suggested that you partition all your cartridges the same. The Amiga reads the RDB, partition table, at boot time only. You should also leave a disk in the drive when you boot.
FLD's software is call Momiga Tools and costs UKŁ 49.95 + 2.50 P&P.
![]()
DiskExpander - Does not work with AFS (Author checking).
Dopus5 - Does not register with AFS (Patch on AmiNet).
Excelsior BBS - Some functions do not work under AFS (Author checking)
Diskspare - Does not work with muFS and AFS at the same time.
Virocop - Does not work with AFS (Author checking).
Note that some HD Prep tools do not support custom file systems, in general, the best thing to do is use rdbprep (On AmiNet) instead.
DOpusReg.lha biz/dopus 3K Opus 5.11 fix for AFS pro
rdp391.lha disk/misc 136K HD prep utility from MicroBotics
![]()
FLD can no longer supply DiskSalv4 or any upgrades. In the US you can get it from IAM :-
DiskSalv4 US$40 Upgrade from DiskSalv3 US$10
Postage will be extra. Please email IAM for further details.
Note that DiskSalv4 will NOT understand AFS V3.0 and above.
![]()
At the moment ReOrgAFS is on hold. It currently seems very unlikely that it will ever be finished and released.
Further details are not available at this time, but that any changes will be announced on the AFS mailing list.
There are some ways to minimise fragmentation.
FLD made an unauthorised announcement that I was working on a DeFrag tool for AFS.
![]()
![]()
AFS caches its reserved area in it's buffers. You should ensure that you have enough buffers for this.
AFS is a secure file system. The order that data is written to the disk is critical. If you use a cache do NOT enable ANY write caching.
Note the 2.4 includes some caching.
![]()
Note that virtual memory managers work best to their own partitions.
![]()
Fragmentation occurs when the allocated blocks are scattered across the disk.
One of the speed benefits come from the fact that AFS maps a file with a-nodes. This carries the details of one chunk or fragment. Ideally a file will be mapped by one a-node. When you "seek" into a file AFS can do this quickly. FFS has to look at the file header and extension blocks.
![]()
DiskValid Analyse <unit>:
This will list all fragmented files.
Do not panic if a number of files is found. You should worry if a number of files has more that 8 fragments.
![]()
The biggest source of fragmentation is appending data to existing files. Log files are prime cases of this. You should make use of rollover log files where possible.
The only way to defragment files is to copy them. The only other way is to backup the partition and restore it. Note that rollover log files are restored as normal files and should be converted back afterwards !
Martin Steigerwald has written a program for doing this. It is available from AmiNet or FLD's FTP server :-
aminet: disk/optim/afsdefragtry.lha
ftp: ftp.flevel.co.uk:/pub/afs/contrib/afsdefragtry.lha
Please do not ask FLD for support on this program.