* [HELP] Tracking down a MD bug
@ 2004-06-24 17:24 Joshua Kwan
2004-06-24 21:46 ` Neil Brown
0 siblings, 1 reply; 3+ messages in thread
From: Joshua Kwan @ 2004-06-24 17:24 UTC (permalink / raw)
To: linux-kernel
Hello,
I've been running benchmarks on a ~2TB software RAID array of varying
configurations using SuSE Linux 9.1's kernel 2.6.4-52-smp. I noticed that
while resyncing a newly created RAID 5 array the kernel would just hang
a few seconds after starting.
I compiled 2.6.7-mm1 just now and the RAID array is busy resyncing, and
still alive, right now.
Are there any MD code changes that could have caused this so I can point
SuSE somewhere? (Well, then again, many SuSE folks are on this list anyway...)
This is on the x86_64 architecture, highmem + SMP + SATA RAID adapter
(although I'm not using it in hardware mode.) I'll provide config/dmesg
from the old kernel on request.
Thanks,
--
Joshua Kwan
^ permalink raw reply [flat|nested] 3+ messages in thread
* Re: [HELP] Tracking down a MD bug
2004-06-24 17:24 [HELP] Tracking down a MD bug Joshua Kwan
@ 2004-06-24 21:46 ` Neil Brown
2004-06-25 18:02 ` Joshua Kwan
0 siblings, 1 reply; 3+ messages in thread
From: Neil Brown @ 2004-06-24 21:46 UTC (permalink / raw)
To: Joshua Kwan; +Cc: linux-kernel
On Thursday June 24, jkwan@rackable.com wrote:
> Hello,
>
> I've been running benchmarks on a ~2TB software RAID array of varying
> configurations using SuSE Linux 9.1's kernel 2.6.4-52-smp. I noticed that
> while resyncing a newly created RAID 5 array the kernel would just hang
> a few seconds after starting.
>
> I compiled 2.6.7-mm1 just now and the RAID array is busy resyncing, and
> still alive, right now.
>
> Are there any MD code changes that could have caused this so I can point
> SuSE somewhere? (Well, then again, many SuSE folks are on this list
> anyway...)
This is definitely a bug in the Suse 2.6.4-52 kernels, and I'm pretty
sure they have fixed it.
NeilBrown
>
> This is on the x86_64 architecture, highmem + SMP + SATA RAID adapter
> (although I'm not using it in hardware mode.) I'll provide config/dmesg
> from the old kernel on request.
>
> Thanks,
>
> --
> Joshua Kwan
>
>
> -
> To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
> the body of a message to majordomo@vger.kernel.org
> More majordomo info at http://vger.kernel.org/majordomo-info.html
> Please read the FAQ at http://www.tux.org/lkml/
^ permalink raw reply [flat|nested] 3+ messages in thread
* Re: [HELP] Tracking down a MD bug
2004-06-24 21:46 ` Neil Brown
@ 2004-06-25 18:02 ` Joshua Kwan
0 siblings, 0 replies; 3+ messages in thread
From: Joshua Kwan @ 2004-06-25 18:02 UTC (permalink / raw)
To: Neil Brown; +Cc: linux-kernel
[-- Attachment #1: Type: text/plain, Size: 427 bytes --]
On Fri, Jun 25, 2004 at 07:46:48AM +1000, Neil Brown wrote:
> > Are there any MD code changes that could have caused this so I can point
> > SuSE somewhere? (Well, then again, many SuSE folks are on this list
> > anyway...)
>
> This is definitely a bug in the Suse 2.6.4-52 kernels, and I'm pretty
> sure they have fixed it.
Thanks, I upgraded the box to 2.6.5-7.75-smp and the bug has vanished.
--
Joshua Kwan
[-- Attachment #2: Digital signature --]
[-- Type: application/pgp-signature, Size: 827 bytes --]
^ permalink raw reply [flat|nested] 3+ messages in thread
end of thread, other threads:[~2004-06-25 18:03 UTC | newest]
Thread overview: 3+ messages (download: mbox.gz follow: Atom feed
-- links below jump to the message on this page --
2004-06-24 17:24 [HELP] Tracking down a MD bug Joshua Kwan
2004-06-24 21:46 ` Neil Brown
2004-06-25 18:02 ` Joshua Kwan
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox