From: Zdenek Kabelac <zkabelac@redhat.com>
To: LVM general discussion and development <linux-lvm@redhat.com>
Cc: Raymond Jennings <shentino@gmail.com>
Subject: Re: [linux-lvm] thin discards
Date: Mon, 22 Jul 2013 11:47:18 +0200 [thread overview]
Message-ID: <51ECFFA6.7010905@redhat.com> (raw)
In-Reply-To: <51EC3936.2020607@redhat.com>
Dne 21.7.2013 21:40, Zdenek Kabelac napsal(a):
> Dne 21.7.2013 13:01, Raymond Jennings napsal(a):
>> Do snapshots behave the same way as thin volumes wrt discards?
>>
Yes, snapshots are just like any other thin volumes.
Just a side note - until I think 3.9 kernel there used to be
bug, which had wrong ref-counting of shared blocks.
Zdenek
next prev parent reply other threads:[~2013-07-22 9:47 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-07-15 15:32 [linux-lvm] thin discards Raymond Jennings
2013-07-16 10:16 ` Zdenek Kabelac
2013-07-16 11:33 ` Raymond Jennings
2013-07-21 7:10 ` Raymond Jennings
2013-07-21 10:47 ` Zdenek Kabelac
2013-07-21 11:01 ` Raymond Jennings
2013-07-21 19:40 ` Zdenek Kabelac
2013-07-22 9:47 ` Zdenek Kabelac [this message]
2013-07-22 10:12 ` Raymond Jennings
2013-07-22 10:16 ` Zdenek Kabelac
2013-07-24 3:12 ` Raymond Jennings
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=51ECFFA6.7010905@redhat.com \
--to=zkabelac@redhat.com \
--cc=linux-lvm@redhat.com \
--cc=shentino@gmail.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).