From Bugzilla Helper: User-Agent: Mozilla/4.0 (compatible; MSIE 6.0; Windows NT 5.1; .NET CLR 1.1.4322) Description of problem: When I have more than 57 multipathing devices, and I make a 'cat /proc/mdstat' I get an Oops with the call trace: Call Trace: [<c022c5a2>] vsnprintf [kernel] 0x2c2 [<c022c5a2>] vsnprintf [kernel] 0x2c2 [<c022c5a2>] vsnprintf [kernel] 0x2c2 [<c022c756>] vsprintf [kernel] 0x16 [<c026d027>] .rodata.str1.1 [kernel] 0x7f02 [<c022c774>] sprintf [kernel] 0x14 [<c026d01f>] .rodata.str1.1 [kernel] 0x7efa [<c01d48c9>] md_status_read_proc [kernel] 0x1d9 [<c026d01f>] .rodata.str1.1 [kernel] 0x7efa [<c0169f70>] proc_file_read [kernel] 0xf0 [<c0146c06>] sys_read [kernel] 0x96 [<c01073c3>] system_call [kernel] 0x33 Version-Release number of selected component (if applicable): kernel-enterprise-2.4.9-e.27 How reproducible: Always Steps to Reproduce: 1. Create more than 57 multipath devices 2. cat /proc/mdstat Additional info:
can you test a kernel newer than e.27 please ? Also which modules are in use ?
I have made an upgrade to kernel 2.4.9e48 and I have the same problem. The modules in use are: Module Size Used by Tainted: P hangcheck-timer 3192 0 (unused) cpqci 30396 6 cpqasm 352224 20 cpqevt 10112 2 [cpqasm] nfsd 80704 8 (autoclean) lockd 61184 1 (autoclean) [nfsd] sunrpc 84464 1 (autoclean) [nfsd lockd] pcmcia_core 57440 0 autofs 13796 0 (autoclean) (unused) bcm5700 73156 4 multipath 11940 61 st 30612 0 (autoclean) sr_mod 17592 0 (autoclean) (unused) cdrom 35520 0 (autoclean) [sr_mod] sg 35076 0 (autoclean) lpfcdd 302728 67 usb-ohci 23456 0 (unused) usbcore 68896 1 [usb-ohci] ext3 71264 5 jbd 55636 5 [ext3] cciss 47424 10 sd_mod 13856 63 scsi_mod 127292 5 [st sr_mod sg lpfcdd cciss sd_mod]
We are aware of this issue and it is fixed in U5, which will ship in a couple of weeks, if you need a fix sooner, i can point you at a beta U5 kernel.
Thanks, what is U5?, can I get a beta?
Sorry, U5 is RedHat v2.1 Update5, I have guessed it. Please, where can I get a beta?
http://people.redhat.com/~jbaron/.private/u5/2.4.9-e.46/
Hi, I have installed 2.4.9-e48, but the error continues.
did you try e.46 as per comment #6?
No, I'm downloading it, I'll probe it at Monday, but if the version e.48 fails, what is the difference with the version e.46?
e.46 is the U5 beta kernel and contains the fix for this issue, during beta we had to release a security erratum, which was e.48. Thus, e.46 has fixes not in e.48 and vice versa.
The bug has been resolved in e.49. Thanks