News for hackers. Stuff that matters.
Re:TFS: A file system built for performance, space efficienc... by gpm on Sunday May 21, 2017 @08:05AM (#14386903)
I think the spec answers your question here

  TFS provides following guarantees:
  
   - Unless data corruption happens, the disk should never be 
     an inconsistent state \footnote{TFS achieves this without using
     journaling or a transactional model.}. Poweroff and the alike
     should not affect the system such that it enters an invalid or
     inconsistent state.
    
  Provided that following premises hold:

   - Any sector (assumed to be a power of two of at least
     \minimumsectorsize bytes) can be read and written atomically,
     i.e. it is never partially written, and interrupting the write
     will never render the disk in a state in which it not already
     is written or retaining the old data.
  
  Data corruption can break these guarantees or premises, and TFS
  encompasses certain measures against such corruption, but they are
  strictly speaking heuristic, like any error detection and correction
  method, as the damage could be across all the disks.

There are no comments on this comment yet.