public inbox for lvm2-cvs@sourceware.org help / color / mirror / Atom feed
From: zkabelac@sourceware.org To: lvm-devel@redhat.com, lvm2-cvs@sourceware.org Subject: LVM2/test t-mdata-strings.sh Date: Sun, 23 Oct 2011 21:24:00 -0000 [thread overview] Message-ID: <20111023212428.22137.qmail@sourceware.org> (raw) CVSROOT: /cvs/lvm2 Module name: LVM2 Changes by: zkabelac@sourceware.org 2011-10-23 21:24:27 Modified files: test : t-mdata-strings.sh Log message: Test with -F flag grep need -F to check what we really want to test. Add better test for existing device. Currently this test DOES NOT work with real /dev handle via udev since our tool does not see such device listet through udev. FIXME: We might be able to see it at least through dmsetup table and use for lvm. Patches: http://sourceware.org/cgi-bin/cvsweb.cgi/LVM2/test/t-mdata-strings.sh.diff?cvsroot=lvm2&r1=1.7&r2=1.8 --- LVM2/test/t-mdata-strings.sh 2011/10/23 15:39:08 1.7 +++ LVM2/test/t-mdata-strings.sh 2011/10/23 21:24:27 1.8 @@ -23,11 +23,14 @@ dmsetup rename "$name" "$PREFIX$pv_ugly" dev1=$(dirname "$dev1")/$PREFIX$pv_ugly +dmsetup table | grep -F "$pv_ugly" + # 'pvcreate, vgcreate on filename with backslashed chars' created=$dev1 # when used with real udev without fallback, it will fail here pvcreate "$dev1" || created=$dev2 -pvs | should grep $dev1 +pvdisplay | should grep -F "$pv_ugly" +should check pv_field "$dev1" pv_name "$dev1" vgcreate $vg "$created" # 'no parse errors and VG really exists' vgs 2>err
next reply other threads:[~2011-10-23 21:24 UTC|newest] Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top 2011-10-23 21:24 zkabelac [this message] -- strict thread matches above, loose matches on Subject: below -- 2011-10-23 15:39 zkabelac 2009-04-03 14:23 wysochanski 2009-03-31 17:30 mbroz 2008-03-12 17:34 mbroz
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=20111023212428.22137.qmail@sourceware.org \ --to=zkabelac@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).