Somsak,<br><br>Did you build your own bnx2 driver? I was getting kernel panics when hitting a certain load with Dell 1950s that also use the bnx2 driver. My solution was to grab the bnx2 source code and build it under the Lustre kernel. If you search the mailing list you'll find the mails dealing with this.
<br><br>If you see bnx2 mentioned in your kernel panic output, then it's probably the cause.<br><br>Thanks,<br><br>Matt<br><br><div><span class="gmail_quote">On 26/11/2007, <b class="gmail_sendername">Somsak Sriprayoonsakul
</b> <<a href="mailto:somsak_sr@thaigrid.or.th">somsak_sr@thaigrid.or.th</a>> wrote:</span><blockquote class="gmail_quote" style="border-left: 1px solid rgb(204, 204, 204); margin: 0pt 0pt 0pt 0.8ex; padding-left: 1ex;">
Hello,<br><br> We have a 4 nodes Lustre Cluster that provides parallel file system<br>for our 192 nodes cluster. The Lustre Cluster are CentOS 4.5, x86_64<br>(Intel series 4000), on HP DL360-G5. The cluster that use it is ROCKS
<br>4.2.1, on the same set of hardware. Our network is Gigabit Ethernet,<br>using bnx2 driver. Lustre setup is<br><br>storage-0-0: mgs+mdt, ost0, ost1 (backup)<br>storage-0-1: mgs+mdt (backup), ost0 (backup), ost1<br>storage-0-2: ost2, ost3 (backup)
<br>storage-0-3: ost2 (backup), ost3<br><br> We're using heartbeat 2.0.8 base on pre-built RPM from CentOS. All<br>backup is configure in the way that it'll not run simultaneously with<br>primary. Note that, we enable flock and quota on Lustre.
<br><br> The problem we have right now is, some of the nodes are randomly<br>panic. This happened about once a week or two week. We tolerate this<br>stupidly by setting kernel.panic=60 and hope that the backup node will
<br>not failed within the time frame, though this is working quite well<br>(base on user feedback, they do not know that the file system is<br>failed). The backup node take-over OST and do recovery for about 250<br>secs then everything back to normal.
<br><br> Anyways we're trying to nail down the reason why the file system is<br>panic. I believe that information above will not suffice to track down<br>the reason. Could someone give me a way to debug or dump some useful
<br>information that I can send to the list for later analysis? Also, does<br>the "RECOVERING" suffice to make the file system stable? Do we need to<br>shutdown the whole system and do e2fsck+lfsck?<br><br> Also, every panic time, quota that was enabled will be disabled (lfs
<br>quota <user> /fs yield "No such process). I have to do quotaoff and<br>quotaon again. It seems that the quota is not being turn on when OST is<br>boot up. Is there a way to always turn this on?<br><br><br> Thank you very much in advance
<br><br><br>--<br><br>-----------------------------------------------------------------------------------<br>Somsak Sriprayoonsakul<br><br>Thai National Grid Center<br>Software Industry Promotion Agency<br>Ministry of ICT, Thailand
<br><a href="mailto:somsak_sr@thaigrid.or.th">somsak_sr@thaigrid.or.th</a><br>-----------------------------------------------------------------------------------<br><br><br>_______________________________________________<br>
Lustre-discuss mailing list<br><a href="mailto:Lustre-discuss@clusterfs.com">Lustre-discuss@clusterfs.com</a><br><a href="https://mail.clusterfs.com/mailman/listinfo/lustre-discuss">https://mail.clusterfs.com/mailman/listinfo/lustre-discuss
</a><br></blockquote></div><br>