Not conclusive, I know, but getting a panic after a brief test stopped
it at that point. :)
>> So, I believe that 2.5.14 is working correctly with 2k ext3
>> filesystems, at least for minimal use. I didn't do any sort of
>> extreme load testing or anything like that, being cautious about it.
>
> I've been testing 2.5.14 pretty hard for a couple of days.
[...]
> ext3-journalled is not happy.
Which probably explains my error, then, as I have not stepped back from
data journaled mode on my system.
[...]
> There's a known race between unmount and writeback which is probably
> impossible to trigger. (see the FIXME at __sync_list). Testing the
> fix for that at present.
Well, unmount wouldn't have happened for quite a long time in the
shutdown process, given it was at the initial 'send SIGTERM' stage...
[...]
> So unless you're a JFS or ext3-journalled user, 2.5.14 is OK.
The latter. Ah, well, at least you know.
[...]
> 04 60 -> line 1120. Yup, I get that one too. I assume you were
> testing with data=journal.
Confirmed.
Daniel
-- No, no, you're not thinking, you're just being logical. -- Niels Bohr - 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/