From: Alasdair G Kergon <agk@redhat.com>
To: lvm-devel@redhat.com
Subject: liblvm2app stripe_size reported wrong
Date: Wed, 4 Jul 2012 21:53:01 +0100 [thread overview]
Message-ID: <20120704205301.GM22022@agk-dp.fab.redhat.com> (raw)
In-Reply-To: <201207041341.29807.benscott@nwlink.com>
On Wed, Jul 04, 2012 at 01:41:29PM -0700, ben wrote:
> I am using:
> value = lvm_lvseg_get_property(lvm_lvseg, "stripesize");
> if (value.is_valid)
> segment->stripe_size = value.value.integer;
> /* now value.value.integer == 128 */
> lvs -o+stripesize
> LV VG Attr LSize Pool Origin Data% Move Log Copy% Convert Stripe
> lvol0 vg1 -wi-a--- 1.00g 64.00k
Well this field is stored in sectors internally, so it's probably just
returning that value directly.
Whether it should be converting or not, I don't know.
This doesn't seem to be documented and so we'll need to look at how other
fields are handled to see if there's a consistent 'rule' here or not.
Alasdair
next prev parent reply other threads:[~2012-07-04 20:53 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-07-04 20:20 liblvm2app stripe_size reported wrong ben
2012-07-04 20:26 ` Alasdair G Kergon
2012-07-04 20:41 ` ben
2012-07-04 20:53 ` Alasdair G Kergon [this message]
2012-07-04 21:01 ` ben
2012-07-04 21:34 ` 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=20120704205301.GM22022@agk-dp.fab.redhat.com \
--to=agk@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.