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 23:14:02 +0100 [thread overview]
Message-ID: <20110715221402.GJ15253@agk-dp.fab.redhat.com> (raw)
In-Reply-To: <201107151301.15551.benscott@nwlink.com>
On Fri, Jul 15, 2011 at 01:01:15PM -0700, ben wrote:
> It isn't a special case. Invalid snaps use capital 'S' in the first column and
> so do merging snaps. The invalid snap 'S' dates back to old versions of LVM.
> Here we have three snaps, the first is invalid, the second is merging and the
> last is normal:
Oh, yes, I see. Curiously the man page used to mention that and it got
replaced with S for merging.
So do you think we should remove that capitalisation, as per the man page
I quoted?
Alasdair
next prev parent reply other threads:[~2011-07-15 22:14 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
2011-07-15 20:01 ` ben
2011-07-15 22:14 ` Alasdair G Kergon [this message]
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=20110715221402.GJ15253@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).