From: Roman Mamedov <rm@romanrm.ru>
To: asj <anand.jain@oracle.com>
Cc: linux-btrfs@vger.kernel.org, hugo@carfax.org.uk, chris.mason@oracle.com
Subject: Re: [PATCH] [RFC] Add btrfs autosnap feature
Date: Thu, 1 Mar 2012 19:23:26 +0600 [thread overview]
Message-ID: <20120301192326.06992f64@natsu> (raw)
In-Reply-To: <1330484376-16178-2-git-send-email-anand.jain@oracle.com>
[-- Attachment #1: Type: text/plain, Size: 1089 bytes --]
On Wed, 29 Feb 2012 10:59:36 +0800
asj <anand.jain@oracle.com> wrote:
> This patch adds btrfs autosnap feature. This creates and
> saves the autosnap config at /etc/autosnap/config.
> Depending on the configuration, autosnap either schedules
> the snapshots by updating the crontab or provides an API
> to trigger the snapshots from the respective applications.
The way I see it, this sort of functionality would look more logical in a
separate userspace daemon, not in 'btrfs' directly.
Such daemon could operate in the background, continuously monitor the FS and
create or remove snapshots based on various criteria (and not depend on cron).
It could even become filesystem-agnostic, over time adding support for other
filesystems with snapshot functionality (ZFS and NILFS2).
It could (and should) be a separate project from the btrfs-tools altogether,
and a separate OS distribution package.
--
With respect,
Roman
~~~~~~~~~~~~~~~~~~~~~~~~~~~
"Stallman had a printer,
with code he could not see.
So he began to tinker,
and set the software free."
[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 198 bytes --]
next prev parent reply other threads:[~2012-03-01 13:23 UTC|newest]
Thread overview: 16+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-02-29 2:59 [RFC] [PATCH] Add btrfs autosnap feature asj
2012-02-29 2:59 ` [PATCH] [RFC] " asj
2012-02-29 3:38 ` Anand Jain
2012-03-01 11:54 ` cwillu
2012-03-02 11:34 ` Arvin Schnell
2012-03-02 12:04 ` cwillu
2012-03-02 12:25 ` Sander
2012-03-05 6:51 ` Anand Jain
2012-03-05 7:07 ` Fajar A. Nugraha
2012-03-05 7:18 ` Arne Jansen
2012-03-05 10:21 ` Anand Jain
2012-03-05 10:28 ` cwillu
2012-03-01 13:23 ` Roman Mamedov [this message]
2012-03-06 7:56 ` [PATCH 1/2] Make find_updated_files to return value instead of printing Anand jain
2012-03-06 7:56 ` [PATCH 2/2] Use transaction id to determin if there is any change in the subvol Anand jain
2012-03-06 9:07 ` [PATCH 2/2 v2] " Anand jain
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=20120301192326.06992f64@natsu \
--to=rm@romanrm.ru \
--cc=anand.jain@oracle.com \
--cc=chris.mason@oracle.com \
--cc=hugo@carfax.org.uk \
--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).