xfs
[Top] [All Lists]

Re: Hangs during filesystem recovery on mount (was: kernel panic "killi

To: Eric Sandeen <sandeen@xxxxxxx>
Subject: Re: Hangs during filesystem recovery on mount (was: kernel panic "killing interrupt handler" and kernel BUG at sched.c:468)
From: Austin Gonyou <austin@xxxxxxxxxxxxxxx>
Date: 03 Oct 2002 21:08:07 -0500
Cc: Federico Sevilla III <jijo@xxxxxxxxxxx>, Linux-XFS Mailing List <linux-xfs@xxxxxxxxxxx>
In-reply-to: <Pine.LNX.4.44.0210032032220.24569-100000@xxxxxxxxxxxxxxxxxxxxxx>
Organization: Coremetrics, Inc.
References: <Pine.LNX.4.44.0210032032220.24569-100000@xxxxxxxxxxxxxxxxxxxxxx>
Sender: linux-xfs-bounce@xxxxxxxxxxx
This sounds very much like my problem from a few weeks ago. 



On Thu, 2002-10-03 at 20:35, Eric Sandeen wrote:
> On Fri, 4 Oct 2002, Federico Sevilla III wrote:
> 
> > Hi everyone,
> > 
> > After another reboot I did an xfs_check on the yet-unrecovered
> > /dev/sda10 and I did not get any messages. An attempt to mount it
> > succeeded. I unmounted /dev/sda10 and did another xfs_check and
> again I
> > did not get any messages, which from the manual page I've
> interpreted as
> > "clean". Because /dev/sda10 was finally unmounted properly the next
> > reboot worked and our server is back online.
> 
> Odd.  Just to make sure I read everything right - xfs itself was
> hanging
> in recovery, and your oopses came from when you tried to sync with
> SysRq?
> 
> And then it sounds like the only thing you did before the mount was
> ultimately successful, was to run xfs_check... which should be a
> read-only
> test, and should not have changed anything about the fs, as far as I
> know.
> 
> I think the most helpful thing (in retrospect) would have been to
> break into kdb, and see where mount was stuck during recovery.
> 
> I'm not sure what to make of this problem...
> 
> -Eric
-- 
Austin Gonyou <austin@xxxxxxxxxxxxxxx>
Coremetrics, Inc.


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