From: "Austin S. Hemmelgarn" <ahferroin7@gmail.com>
To: linux-btrfs@vger.kernel.org,
Ulli Horlacher <framstag@rus.uni-stuttgart.de>
Subject: Re: autoversioning?
Date: Fri, 9 Dec 2016 07:36:59 -0500 [thread overview]
Message-ID: <0219ed6f-e332-5bf1-96b9-f1b1bc09c2e7@gmail.com> (raw)
In-Reply-To: <20161209110213.GA21685@rus.uni-stuttgart.de>
On 2016-12-09 06:02, Ulli Horlacher wrote:
> Is file autoversioning possible with btrfs?
>
> I have a VMS background, where the standard filesystem automatically
> creates a new version for every file that is written.
>
> The number of versions can be controlled globally, on directory or on file
> base.
>
> With btrfs I can create manually a file version (clone) with
> "cp -a --reflink"
> but I want this to be done automatically.
>
> I could set up an incron-job (inotify), but perhaps there is a better,
> easier solution?
>
The first thing that comes to mind is a FUSE module I saw a while back
that does this. AFAIK, it doesn't do any reflinking, but it handles the
COW needed for the versioning itself, so it works on any filesystem, not
just BTRFS (and you could easily run batch deduplication from time to
time on the backing storage so that you have things nicely reflinked).
I sadly don't remember what the FUSE module was called though (I
remember it because I thought the idea was neat, not because I need
something like that), but I do distinctly remember that it exists.
Alternatively, something using fanotify would probably work better than
both options, but it would have to be pretty smart to be reliable.
prev parent reply other threads:[~2016-12-09 12:37 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-12-09 11:02 autoversioning? Ulli Horlacher
2016-12-09 12:36 ` Austin S. Hemmelgarn [this message]
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=0219ed6f-e332-5bf1-96b9-f1b1bc09c2e7@gmail.com \
--to=ahferroin7@gmail.com \
--cc=framstag@rus.uni-stuttgart.de \
--cc=linux-btrfs@vger.kernel.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).