Messages in this thread | | | Date | Thu, 07 Feb 2002 01:23:14 -0800 | From | Andrew Morton <> | Subject | Re: D state processes in 2.4.18-pre7-ac3 |
| |
Andres Salomon wrote: > > Linux incandescent 2.4.18-pre7-ac3 #1 Tue Feb 5 01:00:50 EST 2002 i686 unknown > > I came home today to a bunch of processes apparently hung in jbd's > do_get_write_access(); apparently, something deadlocked, where no > processes could write to one of my partition's journal. That's my > theory, anyways. Several processes had stacks similar to: > > ... > > And, kjournald had the following: > > Call Trace: [<c0131f0a>] [<d08ee6e6>] [<c0112380>] [<d08f08eb>] > [<d08f07c0>] > [<c010f4e8>] > Warning (Oops_read): Code line not seen, dumping what data is available > > Trace; c0131f0a <__wait_on_buffer+6a/90> > Trace; d08ee6e6 <[jbd]journal_commit_transaction+776/dd6> > Trace; c0112380 <schedule+2c0/2f0> > Trace; d08f08ea <[jbd]kjournald+10a/1a0> > Trace; d08f07c0 <[jbd]commit_timeout+0/10>
This is the important part - we sent a write request down the stack and it seems that I/O completion was never signalled.
You should check for any odd messages from the device driver or LVM layers, if the logs made it to disk.
- - To unsubscribe from this list: send the line "unsubscribe linux-kernel" in the body of a message to majordomo@vger.kernel.org More majordomo info at http://vger.kernel.org/majordomo-info.html Please read the FAQ at http://www.tux.org/lkml/
| |