From: Evert Mouw <post-yfx6isLFVcpeoWH0uzbU5w@public.gmane.org>
To: linux-nilfs-u79uwXL29TY76Z2rM5mHXA@public.gmane.org
Subject: time-shifting
Date: Sat, 06 Aug 2011 09:38:26 +0200 [thread overview]
Message-ID: <4E3CEF72.1070303@evert.net> (raw)
Hi,
Yesterday I played a bit with NILFS2 on ubuntu 11.04. It was quite easy
to use, but finding previous versions of a file is still a bit
complicated from a user point of view.
I read a bit about ext3cow, which is currently not actively maintained
anymore. In one of the papers on ext3cow, I read the following:
Other disk file systems provide coarse-grained access to versions through
the creation of namespace tunnels [Hitz et al. 1994] or via mounting
separate logical volumes
[Strunk et al. 2000; Soules et al. 2003]. Some disk file systems provide
no interface
to versions, restricting versioning to internal use only [Rosenblum and
Ousterhout 1992;
Seltzer et al. 1993].
In time-shifting, ext3cow introduces an interface to versioning that
presents a continuous
view of time. Users or applications specify a file name and any point in
time, which
ext3cow scopes to the appropriate snapshot or file version. The
time-shifting interface
allows user-space tools to create snapshots and access versions.
Ext3cow: A Time-Shifting File System for Regulatory Compliance
ZACHARY N. J. PETERSON and RANDAL BURNS
ACM Transactions on Storage, 1(2), May, 2005
http://www.ext3cow.com/ext3cow/Publications.html
A usage scenario is given in a screenshot:
http://www.ext3cow.com/ext3cow/Welcome_files/example1.jpg
I don't think using the "@" symbol for such thinks is a great idea (I
sometimes use it in my filenames) but the ability to use regular tools
to access old versions of files is great.
I think it would be really useful to have access to previous versions of
files without having to go through checkpoints or snapshots of the whole
filesystem / partition. So having something like lshistory or lsversions
for specific files would be great. It could output the versions, the
checkpoints where those versions are available, etc. Maybe direct
retrieval of old versions (cathistory?) could also be possible using
such a path.
Of course the architecture of NILFS is different from ext3cow so I don't
know whether this is even possible. Something like a data structure
linking the different verions of some inode must exist before this can
happen. Just an idea, though.
Thanks for your cool stuff!
Evert
--
To unsubscribe from this list: send the line "unsubscribe linux-nilfs" in
the body of a message to majordomo-u79uwXL29TY76Z2rM5mHXA@public.gmane.org
More majordomo info at http://vger.kernel.org/majordomo-info.html
next reply other threads:[~2011-08-06 7:38 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-08-06 7:38 Evert Mouw [this message]
[not found] ` <4E3CEF72.1070303-yfx6isLFVcpeoWH0uzbU5w@public.gmane.org>
2011-08-07 14:19 ` time-shifting Ryusuke Konishi
[not found] ` <20110807.231959.212685724.ryusuke-sG5X7nlA6pw@public.gmane.org>
2011-08-07 22:17 ` time-shifting Evert Mouw
[not found] ` <4E3F0F16.7020200-yfx6isLFVcpeoWH0uzbU5w@public.gmane.org>
2011-08-08 12:28 ` time-shifting Ryusuke Konishi
[not found] ` <20110808.212859.255403671.ryusuke-sG5X7nlA6pw@public.gmane.org>
2011-08-08 14:02 ` time-shifting Evert Mouw
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=4E3CEF72.1070303@evert.net \
--to=post-yfx6islfvcpeowh0uzbu5w@public.gmane.org \
--cc=linux-nilfs-u79uwXL29TY76Z2rM5mHXA@public.gmane.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).