From: Justin Piszcz <jpiszcz@lucidpixels.com>
To: linux-kernel@vger.kernel.org
Cc: linux-raid@vger.kernel.org, xfs@oss.sgi.com, Neil Brown <neilb@suse.de>
Subject: Kernel 2.6.19.2 New RAID 5 Bug (oops when writing Samba -> RAID5)
Date: Sat, 20 Jan 2007 07:23:39 -0500 (EST) [thread overview]
Message-ID: <Pine.LNX.4.64.0701200718290.29223@p34.internal.lan> (raw)
[-- Attachment #1: Type: TEXT/PLAIN, Size: 3336 bytes --]
My .config is attached, please let me know if any other information is
needed and please CC (lkml) as I am not on the list, thanks!
Running Kernel 2.6.19.2 on a MD RAID5 volume. Copying files over Samba to
the RAID5 running XFS.
Any idea what happened here?
[473795.214705] BUG: unable to handle kernel paging request at virtual
address fffb92b0
[473795.214715] printing eip:
[473795.214718] c0358b14
[473795.214721] *pde = 00003067
[473795.214723] *pte = 00000000
[473795.214726] Oops: 0000 [#1]
[473795.214729] PREEMPT SMP
[473795.214736] CPU: 0
[473795.214737] EIP: 0060:[<c0358b14>] Not tainted VLI
[473795.214738] EFLAGS: 00010286 (2.6.19.2 #1)
[473795.214746] EIP is at copy_data+0x6c/0x179
[473795.214750] eax: 00000000 ebx: 00001000 ecx: 00000354 edx: fffb9000
[473795.214754] esi: fffb92b0 edi: da86c2b0 ebp: 00001000 esp: f7927dc4
[473795.214757] ds: 007b es: 007b ss: 0068
[473795.214761] Process md4_raid5 (pid: 1305, ti=f7926000 task=f7ea9030 task.ti=f7926000)
[473795.214765] Stack: c1ba7c40 00000003 f5538c80 00000001 da86c000 00000009 00000000 0000006c
[473795.214790] 00001000 da8536a8 aa6fee90 f5538c80 00000190 c0358d00 aa6fee88 0000ffff
[473795.214863] d7c5794c 00000001 da853488 f6fbec70 f6fbebc0 00000001 00000005 00000001
[473795.214876] Call Trace:
[473795.214880] [<c0358d00>] compute_parity5+0xdf/0x497
[473795.214887] [<c035b0dd>] handle_stripe+0x930/0x2986
[473795.214892] [<c01146b9>] find_busiest_group+0x124/0x4fd
[473795.214898] [<c03580e0>] release_stripe+0x21/0x2e
[473795.214902] [<c035d233>] raid5d+0x100/0x161
[473795.214907] [<c036b03c>] md_thread+0x40/0x103
[473795.214912] [<c012dbbe>] autoremove_wake_function+0x0/0x4b
[473795.214917] [<c036affc>] md_thread+0x0/0x103
[473795.214922] [<c012da1a>] kthread+0xfc/0x100
[473795.214926] [<c012d91e>] kthread+0x0/0x100
[473795.214930] [<c0103b4b>] kernel_thread_helper+0x7/0x1c
[473795.214935] =======================
[473795.214938] Code: 14 39 d1 0f 8d 10 01 00 00 89 c8 01 c0 01 c8 01 c0
01 c0 89 44 24 1c eb 51 89 d9 c1 e9 02 8b 7c 24 10 01 f7 8b 44 24 18 8d 34
02 <f3> a5 89 d9 83 e1 03 74 02 f3 a4 c7 44 24 04 03 00 00 00 89 14
[473795.215017] EIP: [<c0358b14>] copy_data+0x6c/0x179 SS:ESP
0068:f7927dc4
[473795.215024] <6>note: md4_raid5[1305] exited with preempt_count 2
# mdadm -D /dev/md4
/dev/md4:
Version : 01.00.03
Creation Time : Wed Jan 10 15:58:52 2007
Raid Level : raid5
Array Size : 1562834432 (1490.44 GiB 1600.34 GB)
Device Size : 781417216 (372.61 GiB 400.09 GB)
Raid Devices : 5
Total Devices : 5
Preferred Minor : 4
Persistence : Superblock is persistent
Update Time : Sat Jan 20 07:15:01 2007
State : active
Active Devices : 5
Working Devices : 5
Failed Devices : 0
Spare Devices : 0
Layout : left-symmetric
Chunk Size : 128K
Name : 4
UUID : 7f453e18:893e4dd9:6e810372:4c724f49
Events : 33
Number Major Minor RaidDevice State
0 8 33 0 active sync /dev/sdc1
1 8 81 1 active sync /dev/sdf1
2 8 113 2 active sync /dev/sdh1
3 8 65 3 active sync /dev/sde1
5 8 49 4 active sync /dev/sdd1
[-- Attachment #2: Type: APPLICATION/octet-stream, Size: 7224 bytes --]
next reply other threads:[~2007-01-20 12:23 UTC|newest]
Thread overview: 20+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-01-20 12:23 Justin Piszcz [this message]
2007-01-20 12:46 ` Kernel 2.6.19.2 New RAID 5 Bug (oops when writing Samba -> RAID5) Justin Piszcz
2007-01-22 5:38 ` What is the exacting meaning of Striped_Cache_Size? Liang Yang
2007-01-22 5:38 ` Liang Yang
2007-01-22 6:06 ` Dan Williams
2007-01-22 6:22 ` Liang Yang
2007-01-22 6:22 ` Liang Yang
2007-01-22 16:36 ` Dan Williams
2007-01-22 21:01 ` Kernel 2.6.19.2 New RAID 5 Bug (oops when writing Samba -> RAID5) Chuck Ebbert
2007-01-22 21:59 ` Neil Brown
2007-01-23 1:44 ` Dan Williams
2007-01-23 2:06 ` Neil Brown
2007-01-23 10:56 ` Justin Piszcz
2007-01-23 11:08 ` Michael Tokarev
2007-01-23 11:59 ` Justin Piszcz
2007-01-23 12:48 ` Michael Tokarev
2007-01-23 13:46 ` Justin Piszcz
2007-01-23 17:05 ` Bill Davidsen
2007-01-24 23:37 ` Justin Piszcz
2007-01-26 9:25 ` Andrew Morton
2007-01-26 9:37 ` Justin Piszcz
2007-01-26 12:31 ` Justin Piszcz
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=Pine.LNX.4.64.0701200718290.29223@p34.internal.lan \
--to=jpiszcz@lucidpixels.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-raid@vger.kernel.org \
--cc=neilb@suse.de \
--cc=xfs@oss.sgi.com \
/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.