linux-lvm.redhat.com archive mirror
 help / color / mirror / Atom feed
From: Zdenek Kabelac <zkabelac@redhat.com>
To: LVM general discussion and development <linux-lvm@redhat.com>,
	Far Had <farhadk.it@gmail.com>
Subject: Re: [linux-lvm] CoW under the hood
Date: Mon, 3 Dec 2018 12:39:15 +0100	[thread overview]
Message-ID: <d12ad6cf-1e21-a335-5fbf-63ea064b3093@redhat.com> (raw)
In-Reply-To: <CAB5m+-G1P9HJThW=hckE0yvBN-0VRCbQs4wEom1iO4NcF2U_7w@mail.gmail.com>

Dne 03. 12. 18 v 7:17 Far Had napsal(a):
> Hi,
> I'm trying to understand how LVM thick snapshots work under the hood. I can 
> see that when new write requests are comming to the original volume that has a 
> snapshot, the current contents of storage blocks copy to the snapshot space 
> then the new data overwrites on the volume. No problem so far.
> the question is when I delete a file on a volume that has snapshot, the 
> content is gone on the volume so the pointer which points from volume object 
> to that certain blocks on the volume should now point to empty blocks. On the 
> other hand I can see that the contents of deleted parts from the original 
> volume did not copy to the snapshot space, meaning that the snapshot pointers 
> that were pointing to that blocks on the original volume, still point that 
> direction.
> In other words the pointers from both snapshot and original volume are 
> pointing to the same blocks on the storage media but they don't show the same 
> contents when you mount them on the filesystem.
> Please enlighten me about this situation

Hi

I assume going through some info from this page might put some light into it:

http://people.redhat.com/agk/talks/


In particular http://people.redhat.com/agk/talks/FOSDEM_2005/
from slide 15  there is some info about snapshots you might find useful.

Regards

Zdenek

      reply	other threads:[~2018-12-03 11:39 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2018-12-03  6:17 [linux-lvm] CoW under the hood Far Had
2018-12-03 11:39 ` Zdenek Kabelac [this message]

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=d12ad6cf-1e21-a335-5fbf-63ea064b3093@redhat.com \
    --to=zkabelac@redhat.com \
    --cc=farhadk.it@gmail.com \
    --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).