Linux Device Mapper development
 help / color / mirror / Atom feed
From: Zdenek Kabelac <zdenek.kabelac@gmail.com>
To: device-mapper development <dm-devel@redhat.com>
Cc: devicemapper niko <devicemapper.niko@gmail.com>
Subject: Re: dd between thin provisioned devices
Date: Mon, 28 Jan 2013 10:06:20 +0100	[thread overview]
Message-ID: <51063F8C.3090603@gmail.com> (raw)
In-Reply-To: <CABSD0hKsdtxyQCeZPzFhwpiKY7kmapkPxWJLFidK4VujHnTqTg@mail.gmail.com>

Dne 27.1.2013 11:01, devicemapper niko napsal(a):
> Hi,everyone
> if we dd between thin provisioned devices,
> can we just get allocated blocks copied ?

Nope - devices mapper target operates on block level - not on the filesystem
level - so it has no knowledge about file layout.

What I could eventually imagine is some kind of block compactification (just 
like kernel does for hugepages) - but it's currently not being developed....


> Will the output thin device get fully provisioned?
> I glanced through the dm-thin code,
> it turns out unmapped blocks return zeroed,am i right?

depends on settings - you could have either zeroed block or block
with content left on the disk - i.e. running thin with 1MB block/chunk size
means - before the first use whole 1MB must be zeroed - so it has its price.

> Is there a trick to tell upper applications that all u got are zeroes.
> or should they scan zeroed blocks themselves to trigger WRITE_SAME to reduce
> I/O load?


Documentation/device-mapper/thin-provisioning.txt
see flag: skip_block_zeroing

Eventually for lvm2   lvcreate --zero y|n for thin pool creation.

Zdenek

  reply	other threads:[~2013-01-28  9:06 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2013-01-27 10:01 dd between thin provisioned devices devicemapper niko
2013-01-28  9:06 ` Zdenek Kabelac [this message]
2013-01-28 11:07   ` devicemapper niko
2013-01-28 12:54 ` 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=51063F8C.3090603@gmail.com \
    --to=zdenek.kabelac@gmail.com \
    --cc=devicemapper.niko@gmail.com \
    --cc=dm-devel@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