* mdadm-3.4 regression tests
@ 2016-02-16 4:58 Bruce Dubbs
2016-02-16 17:52 ` Jes Sorensen
0 siblings, 1 reply; 4+ messages in thread
From: Bruce Dubbs @ 2016-02-16 4:58 UTC (permalink / raw)
To: linux-raid
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
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.
-- Bruce Dubbs
linuxfromscratch.org
^ permalink raw reply [flat|nested] 4+ messages in thread
* Re: mdadm-3.4 regression tests
2016-02-16 4:58 mdadm-3.4 regression tests Bruce Dubbs
@ 2016-02-16 17:52 ` Jes Sorensen
2016-02-16 18:24 ` Bruce Dubbs
0 siblings, 1 reply; 4+ messages in thread
From: Jes Sorensen @ 2016-02-16 17:52 UTC (permalink / raw)
To: Bruce Dubbs; +Cc: linux-raid
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
^ permalink raw reply [flat|nested] 4+ messages in thread
* Re: mdadm-3.4 regression tests
2016-02-16 17:52 ` Jes Sorensen
@ 2016-02-16 18:24 ` Bruce Dubbs
2016-02-19 3:25 ` NeilBrown
0 siblings, 1 reply; 4+ messages in thread
From: Bruce Dubbs @ 2016-02-16 18:24 UTC (permalink / raw)
To: Jes Sorensen; +Cc: linux-raid
Jes Sorensen wrote:
> 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?
I'm not sure what you mean by 'proper', but I have
$ ls -ld /var/tmp
drwxrwxrwt 2 root root 4096 Feb 15 22:45 /var/tmp
I'm not concerned about the missing '/var/tmp/log' because I think the
failure triggers a mv to test-logs/log-00raid1 and the message is the
result of a subsequent mv command at the end of the test execution loop.
'/var/tmp/log' does exist while the test is running.
>> 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.
I guess you just missed it. The log above says:
Testing on linux-4.4.1-lfs-7.9-rc1 kernel
The full config is at:
http://anduin.linuxfromscratch.org/~bdubbs/files/config-lfs-7.9-rc1
Thanks for responding.
-- Bruce
^ permalink raw reply [flat|nested] 4+ messages in thread
* Re: mdadm-3.4 regression tests
2016-02-16 18:24 ` Bruce Dubbs
@ 2016-02-19 3:25 ` NeilBrown
0 siblings, 0 replies; 4+ messages in thread
From: NeilBrown @ 2016-02-19 3:25 UTC (permalink / raw)
To: Bruce Dubbs, Jes Sorensen; +Cc: linux-raid
[-- Attachment #1: Type: text/plain, Size: 269 bytes --]
On Wed, Feb 17 2016, Bruce Dubbs wrote:
>
> Testing on linux-4.4.1-lfs-7.9-rc1 kernel
4.4.1 (and 4.4.0) have a bug, fixed in 4.4.2, that probably causes this.
Fixed by
Commit: 1501efadc524 ("md/raid: only permit hot-add of compatible integrity profiles")
NeilBrown
[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 818 bytes --]
^ permalink raw reply [flat|nested] 4+ messages in thread
end of thread, other threads:[~2016-02-19 3:25 UTC | newest]
Thread overview: 4+ messages (download: mbox.gz follow: Atom feed
-- links below jump to the message on this page --
2016-02-16 4:58 mdadm-3.4 regression tests Bruce Dubbs
2016-02-16 17:52 ` Jes Sorensen
2016-02-16 18:24 ` Bruce Dubbs
2016-02-19 3:25 ` NeilBrown
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 NNTP newsgroup(s).