From: Mike Snitzer <snitzer@redhat.com>
To: lvm-devel@redhat.com
Subject: lv-shared
Date: Fri, 19 Mar 2010 15:39:08 -0400 [thread overview]
Message-ID: <20100319193908.GB7345@redhat.com> (raw)
In-Reply-To: <20100315220136.GA3461@redhat.com>
On Mon, Mar 15 2010 at 6:01pm -0400,
Mike Snitzer <snitzer@redhat.com> wrote:
> On Mon, Mar 15 2010 at 4:06pm -0400,
> Mikulas Patocka <mpatocka@redhat.com> wrote:
>
> > On Mon, 15 Mar 2010, Mike Snitzer wrote:
> >
> > > On Mon, Mar 15 2010 at 3:00pm -0400,
> > > Mikulas Patocka <mpatocka@redhat.com> wrote:
> > >
> > > > Hi
> > > >
> > > > Why did you hide the "lv-shared" volume? With this hidden, the size and
> > > > percentage can't be seen.
> > >
> > > You can still see it with: lvs -a
> > >
> > > I'll have to revisit why I made it hidden (aside from the fact that the
> > > associated DM device is also hidden). There was some subtle reason that
> > > had to do with the refactoring of associations when I eliminated the
> > > distinct ->shared_snapshot pointer (otherwise the vg_validate() method
> > > would fail).
> >
> > I know it can be seen with lvs -a, but I think it's inconvenient for the
> > admin:
> > - the admin won't see that there is a shared store taking up space
> > - the admin won't see that the origin is a shared snapshot, he sees 'o',
> > but nothing that refers to that 'o'
> > - the percentage usage of the shared snapshot is hidden
> >
> > I think this information is important and should be displayed with plain
> > "lvs" command without any flags. (for example, the percentage usage is
> > critical, because it can overflow) --- so "lv-shared" shouldn't be hidden.
>
> Sure, not a problem.
>
> I've updated the relevant patch, see:
> http://people.redhat.com/msnitzer/patches/multisnap/lvm2/LVM2-2.02.62/lvm-shared-eliminate-shared_snapshot-in-lv.patch
>
> The lib/metadata/metadata.c:snapshot_count() changes in this updated
> patch address the vg_validate() issue I was seeing. The -shared cow was
> considered to be a normal "snapshot"; as such the vg_validate() checks
> failed.
Mikulas,
I've cleaned up my patches that layer on your a bit, and updated to
2.02.63:
http://people.redhat.com/msnitzer/patches/multisnap/lvm2/LVM2-2.02.63/
This patch saw some changes becuase I moved some functions around:
http://people.redhat.com/msnitzer/patches/multisnap/lvm2/LVM2-2.02.63/lvm-shared-additional-wrappers.patch
One fix associated with the changes is detailed at the end of the
following patch's header:
http://people.redhat.com/msnitzer/patches/multisnap/lvm2/LVM2-2.02.63/lvm-shared-eliminate-shared_snapshot-in-lv.patch
And I implemented the ACCESS_HIDDEN_LV flag we talked about with this
patch:
http://people.redhat.com/msnitzer/patches/multisnap/lvm2/LVM2-2.02.63/lvm-shared-add-ACCESS_HIDDEN_LV-flag.patch
With the result being:
# lvs
LV VG Attr LSize Origin Snap% Move Log Copy% Convert
testlv1 test owi-a- 4.00g
[testlv1-shared] test swi--- 1.00g testlv1 0.01
testlv1_snap test swi-a- 4.00g testlv1
Mike
next prev parent reply other threads:[~2010-03-19 19:39 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-03-15 19:00 lv-shared Mikulas Patocka
2010-03-15 19:29 ` lv-shared Mike Snitzer
2010-03-15 20:06 ` lv-shared Mikulas Patocka
2010-03-15 22:01 ` lv-shared Mike Snitzer
2010-03-19 19:39 ` Mike Snitzer [this message]
2010-03-15 20:28 ` lv-shared Mike Snitzer
2010-03-17 7:30 ` lv-shared Mikulas Patocka
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=20100319193908.GB7345@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.