All of lore.kernel.org
 help / color / mirror / Atom feed
From: Mike Snitzer <snitzer@redhat.com>
To: lvm-devel@redhat.com
Subject: userspace patches for shared snapshots
Date: Wed, 3 Mar 2010 17:37:40 -0500	[thread overview]
Message-ID: <20100303223740.GA12242@redhat.com> (raw)
In-Reply-To: <20100226211702.GA23893@redhat.com>

On Fri, Feb 26 2010 at  4:17pm -0500,
Mike Snitzer <snitzer@redhat.com> wrote:

> On Thu, Feb 25 2010 at 11:52pm -0500,
> Mikulas Patocka <mpatocka@redhat.com> wrote:

> > > # lvs
> > >   LV             VG   Attr   LSize Origin  Snap%  Move Log Copy%  Convert
> > >   testlv1        test owi-a- 4.00g                                       
> > >   testlv1-shared test swi--- 1.00g testlv1 100.00                        
> > > 
> > > NOTE: strikes me as odd that the testlv1-shared Snap% is 100%.  I've
> > > fixed the same with the snapshot-merge code before; will dig deeper in a
> > > bit.
> > 
> > This is actually bug in the kernel, it starts with the smallest possible 
> > size and extends the internal data structures when the first operation is 
> > performed. So, if you ask for status without performing any operation, it 
> > reports 100%.
> > 
> > Thanks for finding it, I overlooked it. I'l fix that.
> 
> Sure, I'll be interested to see your fix.  I'm not clear on what you're
> referring to.

BTW, the patches I posted earlier change this behaviour, in particular
this patch:
http://people.redhat.com/msnitzer/patches/multisnap/lvm2/LVM2-2.02.62/lvm-shared-eliminate-shared_snapshot-in-lv.patch

Now the -shared store is hidden:

# lvs
  LV      VG   Attr   LSize Origin Snap%  Move Log Copy%  Convert
  testlv1 test owi-a- 4.00g                                      

# lvs -a
  LV               VG   Attr   LSize Origin  Snap%  Move Log Copy%  Convert
  testlv1          test owi-a- 4.00g                                       
  [testlv1-shared] test swi--- 1.00g testlv1   0.00                        

You'll also note that Snap% is no longer 100%



  reply	other threads:[~2010-03-03 22:37 UTC|newest]

Thread overview: 14+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2010-02-10 23:59 userspace patches for shared snapshots Mikulas Patocka
2010-02-25 22:13 ` Mike Snitzer
2010-02-26  4:52   ` Mikulas Patocka
2010-02-26 21:17     ` Mike Snitzer
2010-03-03 22:37       ` Mike Snitzer [this message]
2010-03-04 10:11         ` Mikulas Patocka
2010-03-04 13:22           ` Mike Snitzer
2010-03-05 17:47             ` edits for r16 of shared snapshot patches [was: Re: userspace patches for shared snapshots] Mike Snitzer
2010-03-05 17:47               ` Mike Snitzer
2010-03-09  8:41               ` Mikulas Patocka
2010-03-09  8:41                 ` Mikulas Patocka
2010-03-10 20:45                 ` Mike Snitzer
2010-03-09  3:18             ` userspace patches for shared snapshots Mikulas Patocka
2010-03-09  3:38               ` Alasdair G Kergon

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=20100303223740.GA12242@redhat.com \
    --to=snitzer@redhat.com \
    --cc=lvm-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 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.