Hi,
On Mon, Mar 20, 2000 at 10:11:14AM -0800, Marc MERLIN wrote:
> I've been using ext3 alpha release 0.0.2c on several VA servers and
> workstations, and last friday one server died on an oops
>
> There was debugging output that said:
> assertion failure in sync_old_buffers() at buffer.c linue 1956:
> "!bh->b_transaction", which is consistent with the EIP info.
This is a debugging trap which basically means that the background bdflush
sweep found a buffer on the kernel's dirty buffer list which had an active
transaction against it (which means that the buffer should have been on
the protected, journal list).
Was there anything odd prior to this happening? Anything in the logs?
The fact that the fs was remounted with errors suggests that something
else had gone wrong before this (the oops above would not cause the fs
to be marked with errors).
Finally, are you running anything that touches buffers directly on this
disk, or were you doing any heavy delete operations? I have just found a
locking bug: journal_forget() does not take the journal lock, so that
could well explain the problem if you were deleting data at the time.
I'll release a 0.0.2d for 2.2.15 with that fix in place once I've stress
tested things a bit more thoroughly.
Cheers,
Stephen
-
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.tux.org/lkml/
This archive was generated by hypermail 2b29 : Thu Mar 23 2000 - 21:00:33 EST