There could be something more than what was pointed out and fixed earlier. Here is a patch with the changes that were checked in for this, or similar, issue. Check that your version has this applied. If this doesn't help try compiling as 32bit as Garrick suggested.
Brian Wickliffe, Blake W wrote: > Right...but my suspicion is that we are facing something else, since Brian > claims the issue with the 32/64bit was fixed in 3.2.6p21, which we are > already on. > > Unless I am misunderstanding you? > > Blake Wickliffe > Saudi Aramco > ENOD/CSYS/USG HPC Team > (873-4417) > > > -----Original Message----- > From: Garrick [mailto:[email protected]] > Sent: Tuesday, August 18, 2009 7:35 AM > To: Wickliffe, Blake W > Cc: Maui Users > Subject: Re: [Mauiusers] Corrupt node feature list > > That's fine. 32bit maui build works fine on 64bit host talking to a > 64bit pbs_server. > > HPCC/Linux Systems Admin > > On Aug 17, 2009, at 9:23 PM, "Wickliffe, Blake W" <[email protected] > > wrote: > > >> Unfortunately, we are already using 3.2.6p21, and it is on a 64-bit >> system. So, if that's the case, even reverting back to 32-bit might >> not work. >> >> Blake Wickliffe >> Saudi Aramco >> ENOD/CSYS/USG HPC Team >> (873-4417) >> >> >> -----Original Message----- >> From: [email protected] [mailto:mauiusers- >> [email protected]] On Behalf Of Brian Christiansen >> Sent: Monday, August 17, 2009 9:27 PM >> To: Maui Users >> Subject: Re: [Mauiusers] Corrupt node feature list >> >> There was an issue, previously, where you could only have 32 node >> features on a 64bit system without seeing side effects. If you aren't >> using the latest snapshot, you could try it and see if it helps. >> >> From the changelog: >> Maui 3.2.6p21 >> - Fixed 64bit issue. Maui assumed ints were always 8 bytes for 64bit >> systems even though x86_64 ints are still 4 bytes. This lead to >> aliasing >> of large indexed node properties to smaller indexed properties. Maui >> now >> triggers off of sizeof(int). Thanks goes to Alexis Cousein. >> >> Brian Christiansen >> >> Garrick Staples wrote: >> >>> Please start new threads with the "new" button in your email >>> client, not with the "reply" button. >>> >>> On Mon, Aug 17, 2009 at 04:04:21PM +0300, Wickliffe, Blake W alleged: >>> >>> >>>> Hi all, >>>> Has anyone experienced a problem with Maui corrupting the features >>>> list of nodes after a certain number of nodes are added? >>>> >>>> On our cluster, we have 2336 nodes, most of which have only 1 >>>> "Feature" or "Property" in the Torque parlance. However, >>>> immediately upon adding another node, we start seeing things like: >>>> >>>> Features: [[NONE]][checki][datai] >>>> >>>> When doing a "checknode" on various nodes. The problem only gets >>>> worse and more extensive as further nodes are added. Deleting the >>>> nodes from the qmgr brings everything back to normal. >>>> >>>> Any ideas? >>>> >>>> >>> Yes, I've seen this with 64bit builds. Build maui 32bit and it >>> won't happen. >>> >>> >>> --- >>> --------------------------------------------------------------------- >>> >>> _______________________________________________ >>> mauiusers mailing list >>> [email protected] >>> http://www.supercluster.org/mailman/listinfo/mauiusers >>> >>> >> _______________________________________________ >> mauiusers mailing list >> [email protected] >> http://www.supercluster.org/mailman/listinfo/mauiusers >> >> The contents of this email, including all related responses, files >> and attachments transmitted with it (collectively referred to as >> "this Email"), are intended solely for the use of the individual/ >> entity to whom/which they are addressed, and may contain >> confidential and/or legally privileged information. This Email may >> not be disclosed or forwarded to anyone else without authorization >> from the originator of this Email. If you have received this Email >> in error, please notify the sender immediately and delete all copies >> from your system. Please note that the views or opinions presented >> in this Email are those of the author and may not necessarily >> represent those of Saudi Aramco. The recipient should check this >> Email and any attachments for the presence of any viruses. Saudi >> Aramco accepts no liability for any damage caused by any virus/error >> transmitted by this Email. >> _______________________________________________ >> mauiusers mailing list >> [email protected] >> http://www.supercluster.org/mailman/listinfo/mauiusers >> > > The contents of this email, including all related responses, files and > attachments transmitted with it (collectively referred to as "this Email"), > are intended solely for the use of the individual/entity to whom/which they > are addressed, and may contain confidential and/or legally privileged > information. This Email may not be disclosed or forwarded to anyone else > without authorization from the originator of this Email. If you have received > this Email in error, please notify the sender immediately and delete all > copies from your system. Please note that the views or opinions presented in > this Email are those of the author and may not necessarily represent those of > Saudi Aramco. The recipient should check this Email and any attachments for > the presence of any viruses. Saudi Aramco accepts no liability for any damage > caused by any virus/error transmitted by this Email. > _______________________________________________ > mauiusers mailing list > [email protected] > http://www.supercluster.org/mailman/listinfo/mauiusers > _______________________________________________ mauiusers mailing list [email protected] http://www.supercluster.org/mailman/listinfo/mauiusers
