From: ben <benscott@nwlink.com>
To: lvm-devel@redhat.com
Subject: Inconsistent flags of thin volumes and snapshots
Date: Tue, 02 Oct 2012 17:28:42 -0700 [thread overview]
Message-ID: <1540614.udHforCSB6@laptop> (raw)
I have noticed inconsistencies in the flags with regard to
thin volumes. I haven't posted them as bugs yet though because I
am not sure if some are intentional.
The first column of the flags is 'o' when a normal snapshot is taken
of a thin volume but is 'V' when a thin snap is used. I haven't
checked to see if 'O' is used for merging with thin snapshots.
The other issue I have run into is that a thin snapshot doesn't
put an 's' into column 1 or column 7. This makes parsing more
difficult since a thin volume and thin snap look the same in the
flags. It seems that one of the columns could be changed to
an 's' without losing any information. The first column also is
used for merging 'S' so that would probably be the best one.
~# lvs
LV VG Attr LSize Pool Origin Data%
Pool_One MyGroup twi-a-tz- 1.00g 9.96
fat_snap1 MyGroup swi-a-s-- 112.00m thin_vol2 0.00
thin_vol2 MyGroup owi-a-tz- 2.00g Pool_One 4.98
~# lvs
LV VG Attr LSize Pool Origin Data%
Pool_One MyGroup twi-a-tz- 1.00g 9.96
thin_snap1 MyGroup Vwi-a-tz- 2.00g Pool_One thin_vol2 4.98
thin_vol2 MyGroup Vwi-a-tz- 2.00g Pool_One 4.98
Should I post these as bugs?
Thank you.
reply other threads:[~2012-10-03 0:28 UTC|newest]
Thread overview: [no followups] expand[flat|nested] mbox.gz Atom feed
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=1540614.udHforCSB6@laptop \
--to=benscott@nwlink.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.