|To:||Pascal Haakmat <a.haakmat@xxxxxxxxx>|
|Subject:||Re: Oops with 2.4.16|
|From:||Stephen Lord <lord@xxxxxxx>|
|Date:||Thu, 10 Jan 2002 21:10:03 -0600|
|References:||<20020110221155.A912@awacs.dhs.org> <firstname.lastname@example.org> <20020110225711.A1259@awacs.dhs.org> <email@example.com> <20020111023859.A2413@awacs.dhs.org>|
|User-agent:||Mozilla/5.0 (X11; U; Linux i686; en-US; rv:0.9.6) Gecko/20011120|
Pascal Haakmat wrote:
I don't think fs corruption would have much to do with this one, it is a purely in memory10/01/02 16:36, Steve Lord wrote:
circular list. So far as I can see it is always manipulated under the correct locking. I have
a box running a debug kernel sitting in a loop doing the test which Adrian says makes
this happen for him. It has been going for a few hours, so far no problems.
Would you be willing turn on kdb? It only really makes sense if you are able to setup
a serial console. There is a debugger command which will walk the complete list of
inodes in the filesystem.
|<Prev in Thread]||Current Thread||[Next in Thread>|