"Gonyou, Austin" wrote:
> Thanks VERY much for the response. I sure do appreciate it. That is the one
> thing I've not done yet, (removed smp), but I hope to do it soon. Of note,
> it seems to be XFS + SMP, but not EXT2 + SMP, or REISER+ SMP. That much I
> know so far.
yes, I used reiserfs over a year before I changed (of course 8-)) to xfs..
also at SMP machine and I never had problems as described... possibly xfs is
not the basic reason.. I read messegas about 99% cpu running kupdated at a
time where xfs was not released... I think more that xfs points out a problem
deep in the kernel source.. someone of the freaks will solve it next time I
hope, because no one wil run xfs on a SMP server in a view to such problem..
xfs filesystem was mountable after that but files created, changed or opened
after the kupdated starts the long run are completely desapeared or filled
with "@" after reboot.. very strange situation. that means all you or the
system do after the bug occure is complete sensless, no aktion is really done
with the filesystem but you can maybe untar 400MB, go in, and compile
successfull, make install, or anyrthing, you can work with the installed app;
BUT if you reboot all ist lost.