public inbox for lvm2-cvs@sourceware.org
help / color / mirror / Atom feed
From: agk@sourceware.org
To: lvm-devel@redhat.com, lvm2-cvs@sourceware.org
Subject: LVM2 ./WHATS_NEW lib/label/label.c
Date: Wed, 01 Jun 2011 15:30:00 -0000 [thread overview]
Message-ID: <20110601153037.16927.qmail@sourceware.org> (raw)
CVSROOT: /cvs/lvm2
Module name: LVM2
Changes by: agk@sourceware.org 2011-06-01 15:30:36
Modified files:
. : WHATS_NEW
lib/label : label.c
Log message:
Report sector containing label in verbose message.
Patches:
http://sourceware.org/cgi-bin/cvsweb.cgi/LVM2/WHATS_NEW.diff?cvsroot=lvm2&r1=1.2001&r2=1.2002
http://sourceware.org/cgi-bin/cvsweb.cgi/LVM2/lib/label/label.c.diff?cvsroot=lvm2&r1=1.53&r2=1.54
--- LVM2/WHATS_NEW 2011/06/01 12:24:15 1.2001
+++ LVM2/WHATS_NEW 2011/06/01 15:30:36 1.2002
@@ -1,5 +1,6 @@
Version 2.02.86 -
=================================
+ Report sector containing label in verbose message.
Clarify error message when unable to convert an LV into a snapshot of an LV.
Add and use dev_open_readonly and variations.
Do not log a superfluous stack message when the lv is properly processed.
--- LVM2/lib/label/label.c 2011/05/28 09:48:16 1.53
+++ LVM2/lib/label/label.c 2011/06/01 15:30:36 1.54
@@ -156,8 +156,10 @@
dm_list_iterate_items(li, &_labellers) {
if (li->l->ops->can_handle(li->l, (char *) lh,
sector + scan_sector)) {
- log_very_verbose("%s: %s label detected",
- dev_name(dev), li->name);
+ log_very_verbose("%s: %s label detected at "
+ "sector %" PRIu64,
+ dev_name(dev), li->name,
+ sector + scan_sector);
if (found) {
log_error("Ignoring additional label "
"on %s at sector %" PRIu64,
next reply other threads:[~2011-06-01 15:30 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-06-01 15:30 agk [this message]
-- strict thread matches above, loose matches on Subject: below --
2012-02-08 11:12 zkabelac
2006-11-14 15:03 agk
2006-06-08 22:15 agk
2005-03-10 20:23 agk
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=20110601153037.16927.qmail@sourceware.org \
--to=agk@sourceware.org \
--cc=lvm-devel@redhat.com \
--cc=lvm2-cvs@sourceware.org \
/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 read-only IMAP folder(s) and NNTP newsgroup(s).