From: James West <james@terminalsystems.com>
To: linux-btrfs@vger.kernel.org
Subject: Possibility to have a "transient" snapshot?
Date: Fri, 05 Dec 2014 12:27:39 -0600 [thread overview]
Message-ID: <5481F91B.6090700@terminalsystems.com> (raw)
This is just a random idea that popped through my mind while I was
looking into hardening a filesystem against damage, might be
impractical, but the idea seems promising, and well suited to a snapshot
file system.
I'm sure some creative shell scripting could do something like this
already, but I was more looking for something more bulletproof.
General idea would be to have a transient snapshot (optional quota
support possibility here) on top of a base snapshot (possibly readonly).
On system start/restart (whether clean or dirty), the transient snapshot
would be flushed, and the system would restart the snapshot, basically
restarting from the base snapshot. If desired, the transient snapshot
could be promoted to a regular snapshot (say after a software upgrade).
If desired, a different base snapshot could be selected (although I'm
sure the file system would have to be restarted to do this)
From a caching perspective, this could make a noticable performance
difference, since if you're running in a transient snapshot, the file
system can be _extremely_ lazy about committing changes to disk.
For the optional quote support I mentioned, on an unattended box, if the
quota gets exceeded, a system reboot would probably fully correct the
system. (Presumably a log file got out of control in that situation).
next reply other threads:[~2014-12-05 18:37 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-12-05 18:27 James West [this message]
2014-12-05 23:19 ` Possibility to have a "transient" snapshot? Duncan
2014-12-06 5:12 ` Chris Murphy
2014-12-10 19:52 ` James West
2014-12-11 0:58 ` Robert White
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=5481F91B.6090700@terminalsystems.com \
--to=james@terminalsystems.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 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.