From: Jes Sorensen <Jes.Sorensen@redhat.com>
To: Bruce Dubbs <bruce.dubbs@gmail.com>
Cc: linux-raid@vger.kernel.org
Subject: Re: mdadm-3.4 regression tests
Date: Tue, 16 Feb 2016 12:52:08 -0500 [thread overview]
Message-ID: <wrfjio1oczlj.fsf@redhat.com> (raw)
In-Reply-To: <56C2AC87.7000500@gmail.com> (Bruce Dubbs's message of "Mon, 15 Feb 2016 22:58:47 -0600")
Bruce Dubbs <bruce.dubbs@gmail.com> writes:
> I have a problem when trying to document madam-3.4 for the Linux From
> Scratch project. The package builds fine:
>
> tar -xf mdadm-3.4.tar.xz
> cd mdadm-3.4
> make
> make test
>
> Then when I run:
>
> sudo ./test --keep-going --logdir=test-logs --save-logs
>
> Some tests fail and one hangs forever. I can post logs if needed.
>
> Please run './test' as root
> Testing on linux-4.4.1-lfs-7.9-rc1 kernel
> Saving logs to test-logs
> tests/00linear... succeeded
> tests/00multipath... succeeded
> tests/00names... succeeded
> tests/00raid0... succeeded
> tests/00raid1... FAILED - see test-logs/log-00raid1 for details
> cp: cannot stat '/var/tmp/log': No such file or directory
Do you have a proper /var/tmp on that system?
> tests/00raid10... succeeded
> tests/00raid4... succeeded
> tests/00raid5... succeeded
> tests/00raid6... succeeded
> tests/01r1fail... succeeded
> tests/01r5fail... succeeded
> tests/01r5integ... succeeded
> tests/01raid6integ... succeeded
> tests/01replace...
>
> The failure says:
>
> ++ case $* in
> ++ udevadm settle
> +++ cat /proc/sys/dev/raid/speed_limit_max
> ++ p=2000
> ++ echo 20000
> ++ case $* in
> ++ /tmp/mdadm/mdadm-3.4/mdadm --quiet -S /dev/md0
> ++ rv=1
> ++ case $* in
> ++ udevadm settle
> ++ echo 2000
> ++ cat /var/tmp/stderr
> ++ return 1
> ++ mdadm -B /dev/md0 -l 1 --assume-clean -n2 /dev/loop0 /dev/loop1
> ++ rm -f /var/tmp/stderr
> ++ case $* in
> ++ case $* in
> ++ /tmp/mdadm/mdadm-3.4/mdadm --quiet -B /dev/md0 -l 1 --assume-clean
> -n2 /dev/loop0 /dev/loop1
> ++ rv=1
>
> ...
>
> The bigger problem is that 01replace hangs forever. Looking at my
> process list:
> root 16064 2 0 22:45 ? 00:00:00 [md0_raid1]
> root 16093 16049 0 22:45 pts/1 00:00:00
> /tmp/mdadm/mdadm-3.4/mdadm --quiet /dev/md0 --remove /dev/loop1
>
> The --remove operation never completes.
>
> $ cat /proc/mdstat
> Personalities : [raid1] [raid10] [raid6] [raid5] [raid4] [linear] [raid0]
> md0 : active raid1 loop5[5] loop4[4](S) loop3[3] loop2[2] loop1[1](F) loop0[0]
> 19968 blocks super 1.2 [4/4] [UUUU]
>
> Can someone help me figure out why the regression tests give these
> problems. kernel issue? test program issue? internal issue?
>
> The kernel was built with:
>
> CONFIG_MD_AUTODETECT=y
> CONFIG_MD_LINEAR=m
> CONFIG_MD_RAID0=m
> CONFIG_MD_RAID1=y
> CONFIG_MD_RAID10=y
> CONFIG_MD_RAID456=y
> # CONFIG_MD_MULTIPATH is not set
> # CONFIG_MD_FAULTY is not set
>
> Are there other options needed?
>
> Thanks for any help.
Nobody here have a clue what kernel you are running - giving us a
snippet of the .config and no detail about the kernel version is rather
useless.
Jes
next prev parent reply other threads:[~2016-02-16 17:52 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-02-16 4:58 mdadm-3.4 regression tests Bruce Dubbs
2016-02-16 17:52 ` Jes Sorensen [this message]
2016-02-16 18:24 ` Bruce Dubbs
2016-02-19 3:25 ` NeilBrown
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=wrfjio1oczlj.fsf@redhat.com \
--to=jes.sorensen@redhat.com \
--cc=bruce.dubbs@gmail.com \
--cc=linux-raid@vger.kernel.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 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.