xfs
[Top] [All Lists]

Re: [Bug 214] filesystem lockup

To: linux-xfs@xxxxxxxxxxx
Subject: Re: [Bug 214] filesystem lockup
From: Russell Cattelan <cattelan@xxxxxxxxxxx>
Date: 05 Feb 2003 19:52:01 -0600
Cc: bugzilla-daemon@xxxxxxxxxxx
In-reply-to: <200302052130.h15LUxEN006953@xxxxxxxxxxx>
Organization:
References: <200302052130.h15LUxEN006953@xxxxxxxxxxx>
Sender: linux-xfs-bounce@xxxxxxxxxxx
Ok never mind... I looked at a running system and this is the correct
backtrace for those threads.


On Wed, 2003-02-05 at 15:30, bugzilla-daemon@xxxxxxxxxxx wrote:
> http://oss.sgi.com/bugzilla/show_bug.cgi?id=214
> 
> 
> 
> 
> 
> ------- Additional Comments From cattelan@xxxxxxxxxxx  2003-02-05 13:30 
> -------
> Hmm everybody is waiting for IO even your ext3 FS's
> I would look at your scsi system first as these back traces
> seem to suggest errors in that area.
> 
> ^M0xf7cedf64 0xc0116a83 schedule+0x493 (0x0, 0x1, 0xf7cec000, 0xf7cedfd0,
> 0xf7cedfd0)
>                                kernel .text 0xc0100000 0xc01165f0 0xc0116b40
> ^M0xf7cedf8c 0xc0105de5 __down_interruptible+0x75 (0xf7cedfc4, 0xf7cedfc4)
>                                kernel .text 0xc0100000 0xc0105d70 0xc0105e60
> ^M0xf7cedf9c 0xc0105ece __down_failed_interruptible+0xa (0x0, 0x0, 0x1,
> 0xf7cedfd0, 0xf7cedfd0)
>                                kernel .text 0xc0100000 0xc0105ec4 0xc0105ed4
> ^M           0xc0222d65 .text.lock.scsi_error+0x109
>                                kernel .text 0xc0100000 0xc0222c5c 0xc0222d80
> ^M0xf7cedfec 0xc0222b6a scsi_error_handler+0x10a
>                                kernel .text 0xc0100000 0xc0222a60 0xc0222c00
> ^M           0xc0105736 kernel_thread+0x26
>                                kernel .text 0xc0100000 0xc0105710 0xc0105750
> ^MEnter <q> to end, <cr> to continue:
> Stack traceback for pid 13
> ^M0xf7cea000       13        1  0  000  stop  0xf7cea370 scsi_eh_1
> EBP        EIP        Function (args)
> ^M0xf7cebf64 0xc0116a83 schedule+0x493 (0x0, 0x1, 0xf7cea000, 0xf7cebfd0,
> 0xf7cebfd0)
>                                kernel .text 0xc0100000 0xc01165f0 0xc0116b40
> ^M0xf7cebf8c 0xc0105de5 __down_interruptible+0x75 (0xf7cebfc4, 0xf7cebfc4)
>                                kernel .text 0xc0100000 0xc0105d70 0xc0105e60
> ^M0xf7cebf9c 0xc0105ece __down_failed_interruptible+0xa (0x0, 0x0, 0x1,
> 0xf7cebfd0, 0xf7cebfd0)
>                                kernel .text 0xc0100000 0xc0105ec4 0xc0105ed4
> ^M           0xc0222d65 .text.lock.scsi_error+0x109
>                                kernel .text 0xc0100000 0xc0222c5c 0xc0222d80
> ^M0xf7cebfec 0xc0222b6a scsi_error_handler+0x10a
>                                kernel .text 0xc0100000 0xc0222a60 0xc0222c00
> ^M           0xc0105736 kernel_thread+0x26
>                                kernel .text 0xc0100000 0xc0105710 0xc0105750
> ^MEnter <q> to end, <cr> to continue:
> 
> 
> 
> 
> ------- You are receiving this mail because: -------
> You are the assignee for the bug, or are watching the assignee.
-- 
Russell Cattelan <cattelan@xxxxxxxxxxx>


<Prev in Thread] Current Thread [Next in Thread>