From: Mike Snitzer <snitzer@redhat.com>
To: lvm-devel@redhat.com
Subject: LVM2/test t-pvcreate-operation-md.sh
Date: Tue, 19 Jan 2010 11:08:43 -0500 [thread overview]
Message-ID: <20100119160843.GA31041@redhat.com> (raw)
In-Reply-To: <4AAE7942.1040202@redhat.com>
On Mon, Sep 14 2009 at 1:11pm -0400,
Milan Broz <mbroz@redhat.com> wrote:
> Mike Snitzer wrote:
> > We might try loading the raid0 module if it isn't loaded (grep for raid0
> > in /proc/mdstat)? And if that fails skip this test?
>
> I have intentionally all modules unloaded (and do not want sometimes run md tests),
> raid0 is loaded automatically, if md_mod is loaded (then /proc/mdstat exists).
md-mod doesn't provide the raid0 personality; raid0 does. I've changed
the test to attempt loading raid0 if it isn't loaded.
> If md_mod is not there, test fails. For most systems it is loaded in initrd anyway.
>
> That was just quick hack, I think there is problem in mdadm, because it created
> some device node even if md module is not present - but I have no time to debug it now.
I'd be interested to know if you still have problems with the test. If
so we should get to the bottom of it (maybe require a minimum mdadm
version?).
t-pvcreate-operation-md.sh does provide needed testing of LVM2's MD
support so it shouldn't be skipped.
Mike
next prev parent reply other threads:[~2010-01-19 16:08 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-09-13 19:28 LVM2/test t-pvcreate-operation-md.sh mbroz
2009-09-14 1:40 ` Mike Snitzer
2009-09-14 17:11 ` Milan Broz
2010-01-19 16:08 ` Mike Snitzer [this message]
-- strict thread matches above, loose matches on Subject: below --
2010-01-19 15:59 snitzer
2010-04-13 21:42 wysochanski
2010-05-24 15:28 mornfall
2010-07-21 14:12 mornfall
2010-08-12 4:56 snitzer
2010-08-21 15:43 snitzer
2010-09-16 2:39 ` Mike Snitzer
2011-01-05 0:38 mornfall
2011-01-05 1:04 mornfall
2011-01-28 16:12 zkabelac
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=20100119160843.GA31041@redhat.com \
--to=snitzer@redhat.com \
--cc=lvm-devel@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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.