3 ms·
> Basically copying files without actually copying them. For example, when making versioned backups, or when copying a large number of files from production to
by josteink 9y ago
> Basically copying files without actually copying them. For example, when making versioned backups, or when copying a large number of files from production to various development environments.
To me it sounds like you want simple snapshots and backups without the redundancy at the storage level.
So why don't use a filesystem which supports that natively, like ZFS or Btrfs?
- mkj 9y agoDo they handle 64k snapshots?
- lloeki 9y agoThat's one backup every hour for 7+ years. I'm really curious about the use case. Anyway, theoretically[0]: > As you might know btrfs treats subvolumes as filesystems and hence the number of snapshots is indeed limited: namely by the size of files. According to the btrfs wiki the maximum filesize that can be reached is 2^64 byte == 16 EiB But it seems practically you're hitting the mud at ~100 snapshots[1] but be sure to read the reply to that mail as it will depend on the use case and it might turn out to be fine way beyond that. [0]: https://unix.stackexchange.com/questions/140360/practical-limit-on-the-number-of-btrfs-snapshots#147666 https://unix.stackexchange.com/questions/140360/practical-li... [1]: https://www.mail-archive.com/linux-btrfs@vger.kernel.org/msg72385.html https://www.mail-archive.com/linux-btrfs@vger.kernel.org/msg...
- KaiserPro 9y agoNot sure, I have ZFS as a docker storage backend, its yet to crash* *not the best data point I realise....