linux-lvm.redhat.com archive mirror
 help / color / mirror / Atom feed
From: Alasdair G Kergon <agk@redhat.com>
To: ben <benscott@nwlink.com>
Cc: linux-lvm@redhat.com
Subject: Re: [linux-lvm] merging snapshots and lvs bug
Date: Fri, 15 Jul 2011 12:39:01 +0100	[thread overview]
Message-ID: <20110715113901.GE15253@agk-dp.fab.redhat.com> (raw)
In-Reply-To: <201107141946.12747.benscott@nwlink.com>

On Thu, Jul 14, 2011 at 07:46:12PM -0700, ben wrote:
> Currently the first field of the attribute bits are set to 's' for a snapshot 
> and 'S' for a merging snap. Unfortunatly 'S' was used for an invalid snapshot 
> and lvs still uses it both ways. 
 
Invalid snapshot is meant to be shown by I (for invalid) in the 5th position.

              The lv_attr bits are:

              1  Volume  type:  (m)irrored,  (M)irrored  without initial sync,
                 (o)rigin, (O)rigin with merging snapshot, (s)napshot, merging
                 (S)napshot,   (p)vmove,  (v)irtual,  mirror  (i)mage,  mirror
                 (I)mage out-of-sync, under (c)onversion

              5  State:  (a)ctive,  (s)uspended,  (I)nvalid  snapshot, invalid
                 (S)uspended snapshot, mapped (d)evice present without tables,
                 mapped device present with (i)nactive table

If some particular case is giving the wrong output, please show us exactly which
case that is, and how the output looks, together with 'dmsetup info -c',
'dmsetup table' and 'dmsetup status'.

Alasdair

  reply	other threads:[~2011-07-15 11:39 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2011-07-15  2:46 [linux-lvm] merging snapshots and lvs bug ben
2011-07-15 11:39 ` Alasdair G Kergon [this message]
2011-07-15 20:01   ` ben
2011-07-15 22:14     ` Alasdair G Kergon
2011-07-15 23:07       ` ben
2011-07-17 12:30       ` Mike Snitzer

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=20110715113901.GE15253@agk-dp.fab.redhat.com \
    --to=agk@redhat.com \
    --cc=benscott@nwlink.com \
    --cc=linux-lvm@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;
as well as URLs for NNTP newsgroup(s).