Hello, On Wed, 02 Mar 2005 14:38:59 +0400 Brad Campbell <[EMAIL PROTECTED]> wrote:
> Florian Engelhardt wrote: > > > > I activated the raid (/dev/md0), then mounted it, and after > > that i was starting nfs. I was able to mount the share > > on my desktop, creating direcrotys was no problem, but > > as soon as i was copying a file to the share, the server > > freezed. > > Creating files localy (while loged in via ssh) is leading > > to the process is staying in state D. > > Sometimes, when i start nfsd, the system reboots immediately, > > sometimes not. > > At the momment, most of the processes are in state D, reboot > > does not work, and i am not at home, so i am unable to reboot > > the machine manualy. > > Neat trick which I only discovered in desparation last week when > battling a RAID lockup on the -rc4-mm1 kernel on a remote box. > > I was also having hard lockup issues, but reseating all my PCI cards > appear to have rectified that one. Well, there are not much PCI-Cards in this server and reseating them didnt fix it. > As root. echo b > /proc/sysrq-trigger > > Of course only if you have alt-sysrq built in. Thanks for that, i was able to reboot the machine with that trick, but i couldnt find anything bad in the messages file. I made some further tests with the server: Deactivating the raid, and formating the hd�s (hdc and hdd) with reiser4, mounting them and sharing them via nfs and ftp worked great, no freezes, no reboots, everything perfect, even the performance. But as soon, as i activated the raid, the server freezed, or rebooted. Maybe this problem is not a bug in a single component (eg: nfs or reiser4), i think it is the combination of linux raid with reiser4, but i dont know. I will try to get the raid up and running with ext3 and/or jfs. Then we know exactly, if it is the combination of raid and reiser4. Kind regards Florian Engelhardt -- "I may have invented it, but Bill made it famous" David Bradley, who invented the (in)famous ctrl-alt-del key combination - To unsubscribe from this list: send the line "unsubscribe linux-kernel" in the body of a message to [EMAIL PROTECTED] More majordomo info at http://vger.kernel.org/majordomo-info.html Please read the FAQ at http://www.tux.org/lkml/
