The raid0 partition works fine, but it contains a symlink to a directory
on a failing IDE disk. I got a listing of the directory on the RAID0
partition containing the symlink (using color-ls, which does something
with symlinks to see if they are alive), and it froze:
Aug 27 07:36:20 r1032 kernel: hda: status error: status=0x00 { }
Aug 27 07:36:20 r1032 kernel: hda: drive not ready for command
Aug 27 07:36:20 r1032 kernel: hda: status error: status=0x00 { }
Aug 27 07:36:20 r1032 kernel: hda: drive not ready for command
Aug 27 07:36:20 r1032 kernel: ide0: reset: master: error (0x00?)
Aug 27 07:36:20 r1032 kernel: hda: status error: status=0x00 { }
Aug 27 07:36:20 r1032 kernel: end_request: I/O error, dev 03:01 (hda), sector 26
Aug 27 07:36:20 r1032 kernel: hda: drive not ready for command
Aug 27 07:36:20 r1032 kernel: bread in fat_access failed
Aug 27 07:36:20 r1032 kernel: Filesystem panic (dev 03:01).
Aug 27 07:36:20 r1032 kernel: FAT error
Then I tried to umount the RAID0 partition (from a different xterm):
r1032:/# umount /raid
Unable to handle kernel NULL pointer dereference at virtual address 00000008
current->tss.cr3 = 038e2000, %cr3 = 038e2000
*pde = 00000000
Oops: 0000
CPU: 0
EIP: 0010:[<c01293e0>]
EFLAGS: 00010282
eax: 00000000 ebx: c3eac600 ecx: c1520900 edx: c152d7e0
esi: 00000000 edi: c3eac600 ebp: 00000900 esp: c374bf7c
ds: 0018 es: 0018 ss: 0018
Process umount (pid: 869, process nr: 26, stackpage=c374b000)
Stack: 00000000 00000900 c012823d c3eac600 00000000 08040900 c3f4de40 bffffaf4
c01282ff 00000900 00000000 c374a000 0804f461 0804c540 c0128318 0804f460
00000000 c0109a98 0804f460 00000065 0804f460 0804f461 0804c540 bffffaf4
Call Trace: [<c012823d>] [<c01282ff>] [<c0128318>] [<c0109a98>]
Code: 8b 40 08 66 8b 40 2a 25 ff ff 00 00 50 e8 1e bc ff ff 83 c4
Segmentation fault
Here's the decoded version:
Using `/usr/src/linux/System.map' to map addresses to symbols.
>>EIP: c01293e0 <block_fsync+4/1c>
Code: c01293e0 <block_fsync+4/1c>
Code: c01293e0 <block_fsync+4/1c> 8b 40 08 movl 0x8(%eax),%eax
Code: c01293e3 <block_fsync+7/1c> 66 8b 40 2a movw 0x2a(%eax),%ax
Code: c01293e7 <block_fsync+b/1c> 25 ff ff 00 00 andl $0xffff,%eax
Code: c01293f2 <block_fsync+16/1c> 50 pushl %eax
Code: c01293f3 <block_fsync+17/1c> e8 1e bc ff ff call ffffbc30 <_EIP+0xffffbc30>
Code: c01293f8 <cp_old_stat> 83 c4 00 addl $0x0,%esp
Code: c0129401 <cp_old_stat+9/ec> 90 nop
Code: c0129402 <cp_old_stat+a/ec> 90 nop
Code: c0129403 <cp_old_stat+b/ec> 90 nop
There was no resulting filesystem corruption on the RAID0 array. I hope
this helps someone out there! More information is available on request.
-Wes Weimer
-
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@vger.rutgers.edu
Please read the FAQ at http://www.altern.org/andrebalsa/doc/lkml-faq.html