157 processes: 156 sleeping, 1 running, 0 zombie, 0 stopped
CPU states: 6.5% user 22.2% system 0.4% nice 0.0% iowait 70.7%
idle
Mem: 386084k av, 122692k used, 263392k free, 0k shrd, 3608k
buff
19668k active, 89324k inactive
Swap: 514072k av, 0k used, 514072k free 52456k
cached
PID USER PRI NI SIZE RSS SHARE STAT %CPU %MEM TIME CPU COMMAND
526 war 17 0 1072 1068 760 R 12.1 0.2 0:00 0 top
306 war 10 0 712 712 548 S 0.8 0.1 0:00 0 frox
309 war 10 0 700 700 548 S 0.8 0.1 0:00 0 frox
1 root 8 0 216 216 184 S 0.0 0.0 0:08 0 init
2 root 9 0 0 0 0 SW 0.0 0.0 0:00 0 keventd
3 root 9 0 0 0 0 SW 0.0 0.0 0:00 0 kapmd
4 root 19 19 0 0 0 SWN 0.0 0.0 0:00 0
ksoftirqd_CPU
5 root 9 0 0 0 0 SW 0.0 0.0 0:00 0 kswapd
6 root 9 0 0 0 0 SW 0.0 0.0 0:00 0 bdflush
7 root 9 0 0 0 0 SW 0.0 0.0 0:00 0 kupdated
8 root 18446744073709551615 -20 0 0 0 SW< 0.0 0.0
0:00 [mdrecoveryd]
I guess I'll use LVM.
On 2003-03-29T16:03:51,
war <[email protected]> said:
> 8 root 18446744073709551615 -20 0 0 0 SW< 0.0 0.0
> 0:00 [mdrecoveryd]
>
> I guess I'll use LVM.
Thanks for this detailed bug report.
Apparently, that naughty mailing list software apparently has dared to cut out
the "how to reproduce" section, as well as all the other relevant information,
notably exact kernel revision, relevant kernel config settings, compiler used,
the RAID / md configuration involved etc, all of which you certainly provided.
Sincerely,
Lars Marowsky-Br?e <[email protected]>
--
SuSE Labs - Research & Development, SuSE Linux AG
"If anything can go wrong, it will." "Chance favors the prepared (mind)."
-- Capt. Edward A. Murphy -- Louis Pasteur
Config attached.
Using: raidtools-0.90.
But before I even mount anything that is showing up, why?
System Hardware:
CPU Type: Pentium II
CPU Speed: 298.002 MHz
Disk: Maxtor
Ram: 377 MB
Swap: 502 MB
System Software:
Distribution:
audiofile: 0.2.3
automake: 1.4-p6
binutils: 2.13.1
e2fsprogs: 1.27
esound: 0.2.27
gcc: 2.95.3
gettext: 0.11.5
glibc: 2.2.5
glib: 1.2.10
gnome-libs: 1.4.1.7
gtk: 1.2.10
imlib: 1.9.14
kernel: 2.4.20
libtool: 1.3.5
modutils: 2.4.19
openssl: 0.9.6i
orbit: 0.5.17
orbit-idl: 0.6.8
perl: 5.8.0
util-linux: 2.11y
xfree86: 4.2.0
xml2: 2.4.22
xml: 1.8.17
On Sat, 29 Mar 2003, Lars Marowsky-Bree wrote:
> On 2003-03-29T16:03:51,
> war <[email protected]> said:
>
> > 8 root 18446744073709551615 -20 0 0 0 SW< 0.0 0.0
> > 0:00 [mdrecoveryd]
> >
> > I guess I'll use LVM.
>
> Thanks for this detailed bug report.
>
> Apparently, that naughty mailing list software apparently has dared to cut out
> the "how to reproduce" section, as well as all the other relevant information,
> notably exact kernel revision, relevant kernel config settings, compiler used,
> the RAID / md configuration involved etc, all of which you certainly provided.
>
>
> Sincerely,
> Lars Marowsky-Br?e <[email protected]>
>
> --
> SuSE Labs - Research & Development, SuSE Linux AG
>
> "If anything can go wrong, it will." "Chance favors the prepared (mind)."
> -- Capt. Edward A. Murphy -- Louis Pasteur
>
Before I even configured it, this showed up.
How is that relevant?
I compiled the options into the kernel, rebooted, it is at this point
when I get the problem.
On Sat, 29 Mar 2003, Lars Marowsky-Bree wrote:
> On 2003-03-29T16:45:16,
> war <[email protected]> said:
>
> > Config attached.
> > Using: raidtools-0.90.
> > But before I even mount anything that is showing up, why?
>
> How is your RAID configured?
>
>
> Sincerely,
> Lars Marowsky-Br?e <[email protected]>
>
> --
> SuSE Labs - Research & Development, SuSE Linux AG
>
> "If anything can go wrong, it will." "Chance favors the prepared (mind)."
> -- Capt. Edward A. Murphy -- Louis Pasteur
>
On 2003-03-29T16:45:16,
war <[email protected]> said:
> Config attached.
> Using: raidtools-0.90.
> But before I even mount anything that is showing up, why?
How is your RAID configured?
Sincerely,
Lars Marowsky-Br?e <[email protected]>
--
SuSE Labs - Research & Development, SuSE Linux AG
"If anything can go wrong, it will." "Chance favors the prepared (mind)."
-- Capt. Edward A. Murphy -- Louis Pasteur
On 2003-03-29T16:58:29,
war <[email protected]> said:
> Before I even configured it, this showed up.
> How is that relevant?
Because you did not mention it before at all. There was no way of knowing
whether you used a special RAID configuration which triggered the problem.
In any case, I cannot reproduce it. Maybe you should try the latest .21pre
kernel instead, perhaps its doing better for you?
Sincerely,
Lars Marowsky-Br?e <[email protected]>
--
SuSE Labs - Research & Development, SuSE Linux AG
"If anything can go wrong, it will." "Chance favors the prepared (mind)."
-- Capt. Edward A. Murphy -- Louis Pasteur