From: "Brian J. Murrell" <brian@interlinx.bc.ca>
To: linux-lvm@redhat.com
Subject: Re: [linux-lvm] 'snapshot' target still experimental :-(
Date: Wed, 01 Feb 2006 16:51:47 -0500 [thread overview]
Message-ID: <1138830708.15727.20.camel@pc.ilinx> (raw)
In-Reply-To: <1138829354.26648.85.camel@seki.nac.uci.edu>
[-- Attachment #1: Type: text/plain, Size: 992 bytes --]
On Wed, 2006-02-01 at 13:29 -0800, Dan Stromberg wrote:
> It just maintains a series of hardlink trees, so any time a file is
> deleted or added, the actual disk usage increase is only due to the
> changes.
Yes, this is quite a popular technique. To be clear though, a change in
a file does not consume just the amount of the change in the file on the
backup target, but it consumes the entire size of the new file. A
not-so-insignificant amount for very large files. This is where a
(block level or filesystem level) snapshotting scheme would excel as it
would likely only consume an amount of space rounded up to the next
"unit" size more even for changes within a file.
Indeed (and to keep quite on topic), perhaps rather than hardlink trees,
LVM snapshots would be even more space efficient. Maybe that is what
this thread has been about. I just jumped in. Apologies if it was.
b.
--
My other computer is your Microsoft Windows server.
Brian J. Murrell
[-- Attachment #2: This is a digitally signed message part --]
[-- Type: application/pgp-signature, Size: 189 bytes --]
next prev parent reply other threads:[~2006-02-01 21:51 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-02-01 16:37 [linux-lvm] 'snapshot' target still experimental :-( Kevin P. Fleming
2006-02-01 21:29 ` Dan Stromberg
2006-02-01 21:51 ` Brian J. Murrell [this message]
2006-02-01 22:26 ` Kevin P. Fleming
2006-02-01 23:22 ` Ming Zhang
-- strict thread matches above, loose matches on Subject: below --
2006-02-01 16:43 Steffen Plotner
2006-02-01 17:55 ` Kevin P. Fleming
2006-02-01 18:07 Steffen Plotner
2006-02-01 18:30 ` Alasdair G Kergon
2006-02-01 18:39 Steffen Plotner
2006-02-01 20:54 ` Ming Zhang
2006-02-02 3:02 Steffen Plotner
2006-02-02 13:17 ` Imre Gergely
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=1138830708.15727.20.camel@pc.ilinx \
--to=brian@interlinx.bc.ca \
--cc=linux-lvm@redhat.com \
/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).