From: Anand Jain <Anand.Jain@oracle.com>
To: David Pottage <david@electric-spoon.com>
Cc: linux-btrfs <linux-btrfs@vger.kernel.org>,
Chris Mason <chris.mason@oracle.com>
Subject: Re: [RFC] btrfs auto snapshot
Date: Thu, 18 Aug 2011 18:11:11 +0800 [thread overview]
Message-ID: <4E4CE53F.3060908@oracle.com> (raw)
In-Reply-To: <2084d6628f888144198ac8450b470b7c.squirrel@www.chrestomanci.org>
David,
> I think that you need to be careful not to impose your idea of when to
> take snapshots and how long to keep them onto the design. For example
> why take snapshots every 15 minutes? Why not every 10 or every hour?
crontab is anyways changeable by the admin, I think we can have that
flexibility.
> Why treat monthly snapshots as special when it does not fit into most
> working weeks? would weekly be more logical? What about 2 weekly (When
> I worked at Nokia, internal releases where done on Tuesday of each even
> numbered week, so we would have wanted the snapshot taken on that day
> to be retained longer than snapshots taken on other days, or Tuesdays
> in odd numbered weeks.)
agreed. weekly is more important. (I had that in mind but missed it
when writing, sorry for that).
> I think a more flexible design would be to allow the user to specify
> (via a config file for each subvolume) a label for each type of snapshot
> and how long to keep snapshots depending on when they are taken. This
> can be done using syntax similar to crontab:
simple and nice idea. thanks for explaining, will try to get this
in the initial release.
Cheers, Anand
next prev parent reply other threads:[~2011-08-18 10:11 UTC|newest]
Thread overview: 24+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-08-17 2:15 [RFC] btrfs auto snapshot Anand Jain
2011-08-17 9:24 ` Anand Jain
2011-08-17 13:23 ` David Pottage
2011-08-18 10:11 ` Anand Jain [this message]
2011-08-17 19:56 ` Lenz Grimmer
2011-08-17 13:31 ` Matthias G. Eckermann
2011-08-18 10:07 ` Anand Jain
2011-08-17 14:04 ` Dave
2011-08-17 14:50 ` Ken A
2011-08-17 17:38 ` Matthias G. Eckermann
2011-08-17 21:56 ` Matthias G. Eckermann
2012-02-23 9:54 ` Fajar A. Nugraha
2012-03-01 13:48 ` Arvin Schnell
2012-03-01 14:13 ` Fajar A. Nugraha
2011-08-17 15:13 ` snapshot ctime // " Roman Mamedov
2011-08-17 15:56 ` Jérôme Poulin
2011-08-18 10:14 ` Anand Jain
2012-02-23 10:37 ` Hubert Kario
2012-02-23 12:02 ` Anand Jain
2012-02-23 12:13 ` Fajar A. Nugraha
2012-02-23 14:09 ` Matthias G. Eckermann
2012-02-23 13:24 ` Hubert Kario
2012-02-24 6:05 ` Anand Jain
2012-02-24 5:59 ` Fahrzin Hemmati
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=4E4CE53F.3060908@oracle.com \
--to=anand.jain@oracle.com \
--cc=chris.mason@oracle.com \
--cc=david@electric-spoon.com \
--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).