From: Zdenek Kabelac <zkabelac@redhat.com>
To: LVM general discussion and development <linux-lvm@redhat.com>
Subject: Re: [linux-lvm] Bugs in DM_DEVICE_STATUS ioctl no_flush flag settings
Date: Fri, 1 Apr 2016 10:08:42 +0200 [thread overview]
Message-ID: <56FE2C8A.5040309@redhat.com> (raw)
In-Reply-To: <56FD151C.8060500@redhat.com>
Dne 31.3.2016 v 14:16 Zdenek Kabelac napsal(a):
> Dne 21.3.2016 v 13:06 Ming-Hung Tsai napsal(a):
>> Hi,
>
> Hi
>> ------------------------------------------------------------------
>> 3. Fix _metadatapercent_disp to not to handle thin volumes
>>
>
>
> Actually I always planned to 'display' highest_mapped_sector -
> so I did now upstreamed it now (as it seemed arg was unused).
>
> So "Meta%" shows what's been the highest written sector as percent.
> We do plan to add either switch or new field to show those '%' in
> form of byte sizes in future...
>
> Not yet sure how useful or confusing this info is for now...
> But i.e. it's interesting to see how much data is written
> by mkfs.ext4/xfs/reiserfs and how far writes goes on a thin device.
>
> Time for complains...
>
Following here on myself - after longer debate how this would be
understandable by a user - we've concluded we will rather introduce
a new field and leave "Meta%" empty - so there will
be rather a new field 'highest_size/HSize' instead.
Regards
Zdenek
next prev parent reply other threads:[~2016-04-01 8:08 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-03-21 12:06 [linux-lvm] Bugs in DM_DEVICE_STATUS ioctl no_flush flag settings Ming-Hung Tsai
2016-03-31 12:16 ` Zdenek Kabelac
2016-04-01 8:08 ` Zdenek Kabelac [this message]
2016-04-01 16:18 ` Ming-Hung Tsai
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=56FE2C8A.5040309@redhat.com \
--to=zkabelac@redhat.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).