Bdtyktl

I am looking for some virtual file system (e.g. with virtual hard disk) or some other kind of working solution to create archives or data backups with error correction redundancy.

I tried looking for something like Windows 7 VHD, which can be displayed as a new storage device with its own FS, but having a certain configurable percentile of recovery warranty on the files.

In other words, I'd like to have a VHD or something similar, which I can configure setting a certain recovery percentile (e.g. 10%) and the target is the files on this drive could be corrupted up to 10% and they will be recoverable.

To be more precise, the idea is similar to an "encrypted" FS (eg. TrueCrypt), but with redundancy for reliability instead of encryption for privacy and security.

Is there something like this?

I haven't heard of one that works like a block-level filesystem.

Tahoe-LAFS does have this feature but it works more like FTP, it's slow, and really is designed to spread shares amongst multiple hosts.

You could always make your files redundant yourself using a PAR2 tool such as QuickPar.

See https://www.thanassis.space/rsbep.html

This creates extra files with data for error correction using the Reed-Solomon error correction used on audio cd's in the past.

To pitty there no filesystem which uses this technique..

https://en.wikipedia.org/wiki/Reed–Solomon_error_correction

I'm not sure about virtual filesystem but there are many "real" file systems that do error correction

• 
  Bcachefs - It's not yet upstream, full data and metadata checksumming, bcache is the bottom half of the filesystem


• 
  Btrfs – A file system based on B-Trees, created by Oracle Corporation.


• 
  HAMMER – DragonflyBSD's primary filesystem, created by Matt Dillon.


• 
  ReFS (Resilient File System) – A file system by Microsoft with built-in resiliency features.


• 
  Reliance – A transactional file system with CRCs, created by Datalight.


• 
  Reliance Nitro – A tree-based transactional file system with CRCs, developed for high performance and reliability in embedded systems, from Datalight.


• 
  NOVA – The "non-volatile memory accelerated" file system for persistent main memory.


• 
  ZFS – Created by Sun Microsystems for use on Solaris 10 and OpenSolaris, ported to FreeBSD 7.0, NetBSD (as of 08/2009), Linux and to FUSE (not to be confused with the two zFSes from IBM)

https://en.wikipedia.org/wiki/List_of_file_systems#File_systems_with_built-in_fault-tolerance

Of course you can use those in a virtual hard drive and let them handle the error correction. There's no difference whether the file system driver reads from a physical or a virtual drive, since they only receive a stream of bytes.