Forgive me for the ignorance of my question.<p>I'm tired creating backups, or loosing data. Let's be honest, sometimes it happens. Does a filesystem that never deletes/overwrites anything exist?<p>I envision something like an append only filesystem where you all files in your hard drive are under some OS level 'version control' and you can rollback to any version you want. Only files in my home dir would be enough. Obviously once space runs out it would start overwriting the oldest versions.
The expensive version of what you are describing is a vaulting appliance but I won't continue down that path unless you are a bank.<p>The <i>affordable</i> version of what you are describing is a set of NAS class servers that use something like DRBD or Ceph for multi-node replication and rsnapshot for local snapshots/versioning if LVM. If using LVM, then rsnapshot should be configured to save its snapshot where the remote clients can not write to it.<p>Look into setting up Ceph clusters if you plan to build something that will need to scale really large on individual volumes across multiple nodes. Ceph supports creating snapshots. There are pros and cons to solutions such as DRBD, LVM and Ceph. That would be a topic in and of itself. Others here are mentioning ZFS and that is also a popular solution but I have never used it and can't comment on it.<p>In summary if I was asked to build something that would grow to unknown size, require snapshots to roll-back files to a specific date and be fault tolerant I would go with Ceph. As a bonus feature there are libraries and tools to present Ceph volumes as S3-like buckets. There are ansible playbooks for setting up Ceph clusters. Ceph has some really good security features as well.
> Does a filesystem that never deletes/overwrites anything exist?<p>> Obviously once space runs out it would start overwriting the oldest versions.<p>You can’t have both.<p>Also, your system wouldn’t prevent data loss on hardware failures.<p>What you describe is/may be a WORM device (<a href="https://en.wikipedia.org/wiki/Write_once_read_many" rel="nofollow">https://en.wikipedia.org/wiki/Write_once_read_many</a>)
Digital's VMS/OpenVMS had something that was a fair way towards this, in that a file was created with a version number (myfile.txt;1) and when modified, a 2nd file (myfile.txt;2) was created, and so on...<p>In practice we used to work on things then purge when happy with the final changes, as we didn't have that much 'spare' disk, but it was a nice feature.
S3FS with versioning enabled on the S3 bucket would be a pretty low friction way to implement this. You'd also have to enable cross-region replication to deal with your "backups" being in the same place as your working copies.<p>OpenVMS also has a versioning filesystem and a NFS server. The x64 version is available as a private beta, but it's not cheap.<p>Personally, I just keep most stuff in a Google Drive folder and important stuff gets the keep versions forever bit turned on. Everything else goes in a git tree and have some automation to clone it to a reliable utility server when the OS thinks there's plenty of bandwidth available.<p>It's worth noting that the Google Drive solution is the only one that I've been able to get to work reliably across Linux, macOS, Windows, Android, and iOS. I've tried OneDrive, Dropbox, and iCloud Files, but they all have various problems with conflict resolution, annoying upselling, or limited file type support for versioning.
Just for reference, here are links to various old research papers referencing solutions to this scenario:<p>A list of options from a report:<p><a href="https://www.fsl.cs.sunysb.edu/docs/secfs-rpe/index.html#tth_chAp4" rel="nofollow">https://www.fsl.cs.sunysb.edu/docs/secfs-rpe/index.html#tth_...</a><p>VersionFS:<p><a href="https://www.fsl.cs.sunysb.edu/docs/versionfs-msthesis/index.html" rel="nofollow">https://www.fsl.cs.sunysb.edu/docs/versionfs-msthesis/index....</a><p>Elephant:<p><a href="https://citeseerx.ist.psu.edu/viewdoc/summary?doi=10.1.1.70.8488" rel="nofollow">https://citeseerx.ist.psu.edu/viewdoc/summary?doi=10.1.1.70....</a><p><a href="https://citeseerx.ist.psu.edu/viewdoc/summary?doi=10.1.1.129.7767" rel="nofollow">https://citeseerx.ist.psu.edu/viewdoc/summary?doi=10.1.1.129...</a><p>Silver:<p><a href="https://www.usenix.org/system/files/conference/hotstorage16/hotstorage16_wei.pdf" rel="nofollow">https://www.usenix.org/system/files/conference/hotstorage16/...</a><p>Also possibly of interest, vfs:<p><a href="https://github.com/FooSoft/vfs" rel="nofollow">https://github.com/FooSoft/vfs</a>
I imagine something does exist that does this, but I do not know what it is called.<p>I know that overlayfs exists, which could enable this sort of thing by capturing each individual change to the filesystem as a new layer. <a href="https://www.kernel.org/doc/html/latest/filesystems/overlayfs.html?highlight=overlayfs" rel="nofollow">https://www.kernel.org/doc/html/latest/filesystems/overlayfs...</a><p>Btrfs and ZFS can do snapshotting, and I would imagine it could be configured to snapshot at certain intervals or after individual changes to the filesystem or a section of the filesystem, like watched directories.<p><a href="https://wiki.archlinux.org/title/Btrfs#Snapshots" rel="nofollow">https://wiki.archlinux.org/title/Btrfs#Snapshots</a><p><a href="https://docs.oracle.com/cd/E19253-01/819-5461/gbcya/index.html" rel="nofollow">https://docs.oracle.com/cd/E19253-01/819-5461/gbcya/index.ht...</a><p>There's also filesystem-in-userland tech like Fuse which could enable something like this. <a href="https://www.kernel.org/doc/html/latest/filesystems/fuse.html" rel="nofollow">https://www.kernel.org/doc/html/latest/filesystems/fuse.html</a>
On Windows, since 8.1, there is the built in File History. <a href="https://support.microsoft.com/en-us/windows/backup-and-restore-in-windows-352091d2-bb9d-3ea3-ed18-52ef2b88cbef" rel="nofollow">https://support.microsoft.com/en-us/windows/backup-and-resto...</a><p>On macOS, there is Time Machine built in. <a href="https://support.apple.com/en-us/HT201250" rel="nofollow">https://support.apple.com/en-us/HT201250</a><p>ZFS does have the concept of Snapshots but I would not consider that user friendly or useful for version tracking.<p>There is plenty of Version Control systems out there, like Git, again not user friendly for what you want.<p>Dropbox/OneDrive/Google Drive provide various levels of version tracking of changes.<p>I personally use Backblaze (30 days, continuous) and Tarsnap (45 days, nightly) for both off-site and temporal recovery when I really need it. Backblaze is used for "desktop" systems, Tarsnap for "server" systems.
Not exactly what you're asking for, but how about:<p>* use ZFS (or any snapshot capable file system)<p>* trigger snapshots at regular (short) intervals (as chosen by you).<p>ZFS snapshots are very low cost, and you can browse them using your normal file tools. You could reasonably snapshot every (say) 5 minutes, but I wouldn't try every second :)
> I'm tired creating backups, or loosing data. Let's be honest, sometimes it happens. Does a filesystem that never deletes/overwrites anything exist?<p>I use linux and system link the home folder to a Dropbox folder. There is an extended history option [1], so that you can go back a year for any file. I think it’s a reasonably close solution if you do not mind the cost and syncing to cloud.<p>[1]<a href="https://help.dropbox.com/files-folders/restore-delete/extended-version-history" rel="nofollow">https://help.dropbox.com/files-folders/restore-delete/extend...</a>
Look up "append only" filesystems. That'll get you most of the way there, but you'll have to manually reset things to get rid of old files. Or just use a competent backup system.
I think NilFS [0] fits your description, though it is somewhat obscure. It creates a checkpoint with every write, which can mounted after being turned into a snapshot.<p>Although the website seems to have not been updated in a while, it's mailing lists appear to be active. [1]<p><a href="https://nilfs.sourceforge.io/en/" rel="nofollow">https://nilfs.sourceforge.io/en/</a> [0]
<a href="https://marc.info/?l=linux-nilfs" rel="nofollow">https://marc.info/?l=linux-nilfs</a> [1]
Maybe one option would be to host a WebDav share with the Delta-V extension (RFC 3253) backed by Subversion. An alternative to Subversion might me NextCloud which supports automatic versioning and WebDav, but I do not know if it supports versioning through WebDav.<p>I also desire an easy solution to this usecase.
Is Apple Time Machine dead? Many years passed since I used my last one. But anyway,<p><i>I'm tired creating backups</i><p>Have you tried to automate them? Thousands of free and paid software to do that. Setup once, forget until next loss.
I hope this hypothetical OS never needs to use a swap file.<p>More seriously, in a time of unobtrusive automated backups and dirt cheap storage space, why is this such an issue where you want to have this kind of system?
I'd like the opposite - an FS which really deletes everything you command it to so no recovery tool would find (let alone recover) there was anything.