Smart File System: Difference between revisions

Revision as of 13:14, 19 October 2015

Revision as of 13:16, 19 October 2015

Line 35:

Its good performance, better than [[Amiga Fast File System|FFS]], and lack of need for long "validation" in case of an error,<ref name="Hyperion">{{cite web|url=http://blog.hyperion-entertainment.biz/?p=210|title=Hard drive setup for AmigaOS 4.1 Classic}}</ref><ref name="TotalAmiga">{{cite journal|work=Total Amiga|url=http://www.totalamiga.org/pdf/totalamiga_6.pdf|title=Hard Drivin'|page=45|author=Robert Williams|issue=6|year=2000}}</ref> is achieved by grouping multiple directory entries into a single block and by grouping meta data blocks together into clusters.<ref name="Forensics">{{cite book |author=EC-Council |title=Computer Forensics: Investigating Hard Disks, File and Operating Systems |date= 2009 |publisher=Cengage Learning |isbn=1-4354-8350-2 |page=1-16 |chapter=Understanding File Systems and Hard Disks |url=http://news.asis.io/sites/default/files/Investigating_Hard_Disks_File__Operating_Systems.pdf }}</ref> A [[free space bitmap|bitmap]] is used to keep track of free space, and file data is kept track of using extents arranged into a [[B+ tree]] structure.<ref name="Forensics" />

Integrity is maintained by keeping a [[transaction log]] of all changes made to metadata over a certain period of time.<ref name="Forensics" /> The log is written to disk first into free space and then meta data blocks are overwritten directly. Should the system crash, the next time the filesystem is mounted it will notice the uncompleted operation and roll it back to the last known consistent state. For performance reasons, only metadata integrity is ensured. Actual data in files can still be corrupted if a write operation is terminated half way through.<ref>{{cite web |url=http://www.amiga-stuff.com/text/filesystems/SFS.guide |author=Hendrikx, J |title=Smart Filesystem documentation |yeardate=19994 August 1998 |archive-url=https://web.archive.org/web/20040707174441/http://www.amiga-stuff.com/text/filesystems/SFS.guide |archivedate=2004-07-07 }}</ref> Unlike the original Amiga filesystems, [[Amiga Fast File System|FFS]] and [[Amiga Old File System|OFS]], filesystem integrity is very rarely compromised by this.

One feature of SFS that is almost unique among Amiga filesystems is its ability to defragment itself while the filesystem is in use, even for locked files.<ref name="Forensics" /> The defragmentation process is almost completely stateless (apart from the ___location it is working on), which means it can be stopped and started instantly. During defragmentation data integrity is ensured of both meta data and normal data. The filesystem may attempt to move a whole file to a different ___location when fragmentation is going to occur otherwise.<ref name="Forensics2">{{cite book|author1=Husrev Taha Sencar|author2=Nasir Memon|title=Digital Image Forensics: There is More to a Picture than Meets the Eye|url=httphttps://books.google.com/books?id=PzP9ViF8oAIC&pg=PA130 |date=1 August 2012|publisher=Springer Science & Business Media|isbn=978-1-4614-0757-7|page=130}}</ref>

The filesystem offers a directory containing deleted files for recovery.<ref name="TotalAmiga" />

Line 63:

* [[File system]]

* [[List of file systems]]

* [[Amiga Rigidrigid Diskdisk Blockblock]]

==References==