public inbox for lvm2-cvs@sourceware.org help / color / mirror / Atom feed
From: mornfall@sourceware.org To: lvm-devel@redhat.com, lvm2-cvs@sourceware.org Subject: LVM2/test t-mirror-lvconvert.sh Date: Tue, 06 Apr 2010 22:22:00 -0000 [thread overview] Message-ID: <20100406222227.3341.qmail@sourceware.org> (raw) CVSROOT: /cvs/lvm2 Module name: LVM2 Changes by: mornfall@sourceware.org 2010-04-06 22:22:26 Modified files: test : t-mirror-lvconvert.sh Log message: Put back the `lvconvert -m+1 --mirrorlog disk' test in t-lvconvert-mirror.sh. Patches: http://sourceware.org/cgi-bin/cvsweb.cgi/LVM2/test/t-mirror-lvconvert.sh.diff?cvsroot=lvm2&r1=1.20&r2=1.21 --- LVM2/test/t-mirror-lvconvert.sh 2010/04/06 18:13:43 1.20 +++ LVM2/test/t-mirror-lvconvert.sh 2010/04/06 22:22:26 1.21 @@ -271,14 +271,14 @@ lvs -a -o+devices $vg check_mirror_count_ $vg/$lv1 2 not_sh check_mirror_log_ $vg/$lv1 -# FIXME Next test broken - code does allocation in several pieces -#lvconvert -m+1 --mirrorlog disk -i1 $vg/$lv1 $dev3:0 $dev4 -#lvs -a -o+devices $vg -#check_no_tmplvs_ $vg/$lv1 -#check_mirror_count_ $vg/$lv1 3 -#check_mirror_log_ $vg/$lv1 -#mimages_are_redundant_ $vg $lv1 -#mirrorlog_is_on_ $vg/$lv1 $dev3 +# FIXME on next line, specifying $dev3:0 $dev4 (i.e log device first) fails (!) +lvconvert -m+1 --mirrorlog disk -i1 $vg/$lv1 $dev4 $dev3:0 +lvs -a -o+devices $vg +check_no_tmplvs_ $vg/$lv1 +check_mirror_count_ $vg/$lv1 3 +check_mirror_log_ $vg/$lv1 +mimages_are_redundant_ $vg $lv1 +mirrorlog_is_on_ $vg/$lv1 $dev3 check_and_cleanup_lvs_ # ---
next reply other threads:[~2010-04-06 22:22 UTC|newest] Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top 2010-04-06 22:22 mornfall [this message] -- strict thread matches above, loose matches on Subject: below -- 2010-04-28 17:46 jbrassow 2010-04-06 23:04 mornfall 2010-04-06 18:13 agk 2010-04-06 16:31 agk 2010-03-29 16:50 mornfall 2010-03-25 12:14 agk 2010-03-25 11:47 agk 2009-12-10 22:06 jbrassow 2009-05-22 14:56 mbroz 2009-05-19 15:47 wysochanski 2008-04-23 18:28 wysochanski
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=20100406222227.3341.qmail@sourceware.org \ --to=mornfall@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: linkBe 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).