public inbox for lvm2-cvs@sourceware.org
help / color / mirror / Atom feed
From: wysochanski@sourceware.org
To: lvm-devel@redhat.com, lvm2-cvs@sourceware.org
Subject: LVM2 ./WHATS_NEW tools/lvresize.c
Date: Thu, 15 Jan 2009 14:44:00 -0000 [thread overview]
Message-ID: <20090115144450.27778.qmail@sourceware.org> (raw)
CVSROOT: /cvs/lvm2
Module name: LVM2
Changes by: wysochanski@sourceware.org 2009-01-15 14:44:49
Modified files:
. : WHATS_NEW
tools : lvresize.c
Log message:
Fix fsadm lvresize for filesystem block sizes != 1024.
Fixes rhbz 480022.
Patches:
http://sourceware.org/cgi-bin/cvsweb.cgi/LVM2/WHATS_NEW.diff?cvsroot=lvm2&r1=1.1020&r2=1.1021
http://sourceware.org/cgi-bin/cvsweb.cgi/LVM2/tools/lvresize.c.diff?cvsroot=lvm2&r1=1.99&r2=1.100
--- LVM2/WHATS_NEW 2009/01/10 17:09:40 1.1020
+++ LVM2/WHATS_NEW 2009/01/15 14:44:48 1.1021
@@ -1,5 +1,6 @@
Version 2.02.44 -
====================================
+ Fix fsadm failure with block size != 1K.
Fix pvs segfault when run with orphan PV and some VG fields.
Display a 'dev_size' of zero for missing devices in reports.
Add pv_mda_size to pvs and vg_mda_size to vgs.
--- LVM2/tools/lvresize.c 2008/11/03 22:14:30 1.99
+++ LVM2/tools/lvresize.c 2009/01/15 14:44:49 1.100
@@ -144,7 +144,7 @@
return 0;
}
- if (dm_snprintf(size_buf, SIZE_BUF, "%" PRIu64,
+ if (dm_snprintf(size_buf, SIZE_BUF, "%" PRIu64 "K",
(uint64_t) lp->extents * vg->extent_size / 2) < 0) {
log_error("Couldn't generate new LV size string");
return 0;
@@ -635,7 +635,7 @@
lp->lv_name);
return ECMD_FAILED;
}
- if (dm_snprintf(size_buf, SIZE_BUF, "%" PRIu64,
+ if (dm_snprintf(size_buf, SIZE_BUF, "%" PRIu64 "K",
(uint64_t) lp->extents * vg->extent_size / 2) < 0) {
log_error("Couldn't generate new LV size string");
return ECMD_FAILED;
next reply other threads:[~2009-01-15 14:44 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-01-15 14:44 wysochanski [this message]
-- strict thread matches above, loose matches on Subject: below --
2012-04-11 12:40 zkabelac
2012-04-11 12:36 zkabelac
2012-02-08 10:56 zkabelac
2012-01-09 12:31 zkabelac
2011-12-01 0:13 jbrassow
2010-03-20 3:44 snitzer
2008-09-18 18:52 agk
2008-04-01 22:15 wysochanski
2004-11-18 19:49 agk
2004-05-24 15:58 agk
2004-05-11 18:47 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=20090115144450.27778.qmail@sourceware.org \
--to=wysochanski@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).