All of lore.kernel.org
 help / color / mirror / Atom feed
From: Zdenek Kabelac <zkabelac@redhat.com>
To: lilofile <lilofile@aliyun.com>,
	device-mapper development <dm-devel@redhat.com>,
	Mike Snitzer <msnitzer@redhat.com>,
	Ondrej Kozina <okozina@redhat.com>,
	"Alasdair G. Kergon" <agk@redhat.com>
Subject: Re: reply： Thinly-Provisioned Logical Volumes
Date: Wed, 24 Sep 2014 09:02:40 +0200	[thread overview]
Message-ID: <54226C90.4080305@redhat.com> (raw)
In-Reply-To: <ae586129-fc3a-41fe-8f2e-f3124c5ff58d@aliyun.com>

Dne 24.9.2014 v 04:11 lilofile napsal(a):
> When I test thinly-provisioned logical volumes,I use dd if=/dev/zero of=/dev/mapper/mythinvolume count=1 bs=4k
> I only write 4k data in mythinvolume.but In thin_map functions, I found there are really  4K data written,but I found more read IO,probably dozens of read io. who issue these IO?
>

Hi

I'd have guessed those I/O are likely metadata update related - at most every 
second metadata are synchronized to your metadata storage volume.
(Thin pool consists of _tdata data volume where provisioned chunks are located 
and _tmeta metadata volume).

And btw you could use tools like thin_dump  to explore how is your pool used,
which chunks belong to which volume, which are share and so on....

Regards

Zdenek

  reply	other threads:[~2014-09-24  7:02 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2014-09-20 14:19 Thinly-Provisioned Logical Volumes lilofile
2014-09-22  7:02 ` Zdenek Kabelac
2014-09-22 12:38 ` Mike Snitzer
2014-09-23 13:51 ` reply： " lilofile
2014-09-23 14:07   ` Zdenek Kabelac
2014-09-24  2:11   ` lilofile
2014-09-24  7:02     ` Zdenek Kabelac [this message]
2014-09-24  8:37     ` 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=54226C90.4080305@redhat.com \
    --to=zkabelac@redhat.com \
    --cc=agk@redhat.com \
    --cc=dm-devel@redhat.com \
    --cc=lilofile@aliyun.com \
    --cc=msnitzer@redhat.com \
    --cc=okozina@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 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.