From: Anand Jain <Anand.Jain@oracle.com>
To: Hubert Kario <hka@qbs.com.pl>
Cc: linux-btrfs <linux-btrfs@vger.kernel.org>,
Chris Mason <chris.mason@oracle.com>
Subject: Re: [RFC] btrfs auto snapshot
Date: Thu, 23 Feb 2012 20:02:38 +0800 [thread overview]
Message-ID: <4F462ADE.4040507@oracle.com> (raw)
In-Reply-To: <1483419.CO5JBoDgFX@bursa22>
autosnap code is available either end of this week or early
next week and what you will notice is autosnap snapshots
are named using uuid.
Main reason to drop time-stamp based names is that,
- test (clicking on Take-snapshot button) which took more
than one snapshot per second was failing.
- a more descriptive creation time is available using a
command line option as in the example below.
-----
# btrfs su list -t tag=@minute,parent=/btrfs/sv1 /btrfs
/btrfs/.autosnap/6c0dabfa-5ddb-11e1-a8c1-0800271feb99 Thu Feb 23 13:01:18 2012 /btrfs/sv1 @minute
/btrfs/.autosnap/5669613e-5ddd-11e1-a644-0800271feb99 Thu Feb 23 13:15:01 2012 /btrfs/sv1 @minute
-----
As of now code for time-stamp as autosnap snapshot name is
commented out, if more people wanted it to be a time-stamp
based names, I don't mind having that way. Please do let me know.
Thanks, Anand
On Thursday 23,February,2012 06:37 PM, Hubert Kario wrote:
> On Wednesday 17 of August 2011 10:15:46 Anand Jain wrote:
>> btrfs auto snapshot feature will include:
>> Initially:
> <snip>
>> - snapshot destination will be subvol/.btrfs/snapshot@<time> and
>> snapshot/.btrfs/snapshot@<time> for subvolume and snapshot
>> respectively
>
> Is there some reason not to use the format used by shadow_copy2 overlay for
> Samba? (The one providing Shadow Volume Copy functionality for Windows
> clients):
>
> Current date in this format you get like this:
>
> @GMT-`date -u '+%Y.%m.%d-%H.%M.%S'`
>
> For example: @GMT-2012.02.23-10.34.32
>
> This way, when the volume is exported using Samba, you can easily export
> past copies too, without creating links.
>
> Regards,
next prev parent reply other threads:[~2012-02-23 12:02 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
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 [this message]
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=4F462ADE.4040507@oracle.com \
--to=anand.jain@oracle.com \
--cc=chris.mason@oracle.com \
--cc=hka@qbs.com.pl \
--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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.