All of lore.kernel.org
 help / color / mirror / Atom feed
From: "Wolfgang Weisselberg" <uzx87lvfmukwc001@sneakemail.com>
To: linux-lvm@sistina.com
Subject: Re: [linux-lvm] read-only media in a LVM?
Date: Mon Jun 23 16:23:01 2003	[thread overview]
Message-ID: <3926-58764@sneakemail.com> (raw)
In-Reply-To: <C42D120999B1CC4C886B6BB2832F356019BF8D@hermes.genomatica.com>

Sean P. Kane wrote 36 lines:

> Does a snapshot create a copy of all the files in memory?

Nope.  And not in memory either.

> Just the files that changed?

Nope, LVM is filesystem-agnostic, and that would have to change
that.  More code, more errors, less usability.

Additionally, what would you do with metadata, like used
filesystem blocks and timestamps and filenames?

Or with a 1 TB file where just 1 bit was changed?

> Or just the file blocks or contents (i.e. diffs) that have
> changed?

Blocks of (default) 32Kb of raw disk.  They are written to the
snapshot.  However, the tables of which blocks were written are
kept in RAM, so a read request on the snapshot redirects only the
unchanged blocks to the original (HD/CD) and gets the changed
blocks out of the snapshot storage.

> So, would the snapshot have to be the same size as the cdrom or
> could it be smaller?

MUCH smaller. Unless you insist on changing something in every
32KB block of the CDrom.

-Wolfgang

  reply	other threads:[~2003-06-23 16:23 UTC|newest]

Thread overview: 14+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2003-06-23 12:51 [linux-lvm] read-only media in a LVM? Sean P. Kane
2003-06-23 16:23 ` Wolfgang Weisselberg [this message]
  -- strict thread matches above, loose matches on Subject: below --
2003-06-24 18:49 Sean P. Kane
2003-06-24 11:27 Sean P. Kane
2003-06-23 17:13 Sean P. Kane
2003-06-23 17:41 ` Kevin P. Fleming
2003-06-23 18:54   ` Sean P. Kane
2003-06-23 19:35     ` Wolfgang Weisselberg
2003-06-23 20:10     ` Kevin P. Fleming
2003-06-16  8:35 Sean P. Kane
2003-06-16  8:52 ` Joe Thornber
2002-05-27 18:30 Ami Fischman
2002-05-28  3:40 ` Joe Thornber
2002-05-28  3:44 ` Joe Thornber

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=3926-58764@sneakemail.com \
    --to=uzx87lvfmukwc001@sneakemail.com \
    --cc=linux-lvm@sistina.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 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.