From: Ryusuke Konishi <ryusuke-sG5X7nlA6pw@public.gmane.org>
To: rich.pixley-C65YXLrEp3M@public.gmane.org
Cc: linux-nilfs-u79uwXL29TY76Z2rM5mHXA@public.gmane.org
Subject: Re: newbie question
Date: Fri, 21 May 2010 07:30:26 +0900 (JST) [thread overview]
Message-ID: <20100521.073026.88488718.ryusuke@osrg.net> (raw)
In-Reply-To: <4BF5A6E0.6040703-C65YXLrEp3M@public.gmane.org>
Hi,
On Thu, 20 May 2010 14:17:20 -0700, Rich Pixley wrote:
> Can nilfs "roll back" to a previous state of the file system?
>
> For example, at some time = T(N), I have a file system in a known good
> state. So I check point it before taking a risky action. Then I take a
> risky action which leads me to the file system state at T(N+1).
>
> Sometimes, my risky action will be fine and I'll want to continue on.
> Other times, my risky action will result in a polluted, useless
> collection of data which I would like to discard.
>
> I understand that at time T(N+1) nilfs will allow me to create a
> checkpoint of T(N) which can be mounted read-only. What I'm asking is
> if nilfs can discard the state at T(N+1) and "roll back" to the state at
> T(N) as though T(N+1) had never happened.
>
> Can nilfs do this kind of "roll back"?
>
> --rich
The "roll back" feature is one of our todo items, and not yet
supported. At present, nilfs needs user's "copy back" operation to
roll back the state at T(N).
I think offline rollback is feasible, but I don't know whether it's
true of online rollback because the online rollback needs to discard
memory states of some sort or instead ensure consistency for the
processes which reside in the namespace of nilfs. This may be done
in the same manner as file removal, but I don't know yet.
Cheers,
Ryusuke Konishi
--
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 prev parent reply other threads:[~2010-05-20 22:30 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-05-20 21:17 newbie question Rich Pixley
[not found] ` <AANLkTikeGWuCeGVELFipNnA_EQ-UHm4fbTvi6-qBiRBi@mail.gmail.com>
[not found] ` <AANLkTikeGWuCeGVELFipNnA_EQ-UHm4fbTvi6-qBiRBi-JsoAwUIsXosN+BqQ9rBEUg@public.gmane.org>
2010-05-20 22:18 ` Jérôme Poulin
[not found] ` <4BF5A6E0.6040703-C65YXLrEp3M@public.gmane.org>
2010-05-20 22:30 ` Ryusuke Konishi [this message]
[not found] ` <20100521.073026.88488718.ryusuke-sG5X7nlA6pw@public.gmane.org>
2010-05-27 17:40 ` K. Richard Pixley
[not found] ` <4BFEAE99.3030100-pBcMlXao8V4@public.gmane.org>
2010-05-28 5:55 ` Jiro SEKIBA
[not found] ` <4C00071A.4010508@noir.com>
[not found] ` <4C00071A.4010508-pBcMlXao8V4@public.gmane.org>
2010-05-28 21:14 ` K. Richard Pixley
2010-05-28 21:16 ` K. Richard Pixley
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=20100521.073026.88488718.ryusuke@osrg.net \
--to=ryusuke-sg5x7nla6pw@public.gmane.org \
--cc=linux-nilfs-u79uwXL29TY76Z2rM5mHXA@public.gmane.org \
--cc=rich.pixley-C65YXLrEp3M@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