<br><br><div class="gmail_quote">On Feb 2, 2008 3:04 AM, Garrick Staples <<a href="mailto:garrick@usc.edu">garrick@usc.edu</a>> wrote:<br><blockquote class="gmail_quote" style="border-left: 1px solid rgb(204, 204, 204); margin: 0pt 0pt 0pt 0.8ex; padding-left: 1ex;">
On Sat, Feb 02, 2008 at 02:45:51AM -0500, Glen Beane alleged:<br><div><div></div><div class="Wj3C7c">> I've just checked in some changes into trunk that increase the PBS_JOBBASE<br>> constant from 11 to 61. This allows for 64 char .JB and .SC files on<br>
> pbs_server/pbs_mom<br>><br>> the previous 14 char limit was too small when you combine large job sequence<br>> nubmers and large job arrays - we just couldn't hash those 11 characters<br>> enough to make the neessary number of unique file names.<br>
><br>> This should help the job arrays scale much better.<br>><br>> .JB files with the old size for their jobbase array are automatically<br>> upgraded when pbs_server starts<br>> we used a similar auto upgrader from 2.1.x to 2.2.0. the only down side is<br>
> if you upgrade to 2.3.x you wouldn't be able to recover your jobs if you<br>> downgrade back to 2.2.x (they will be renamed as .BD files I think)<br><br><br></div></div>Would it make sense to rename the existing files when pbs_server or pbs_mom<br>
restarts?<br></blockquote></div><br>rename the .JB or .JC files so the jobid part of the prefix isn't truncated at 11 characters? I think this might make sense, and it would be easy to do in the job file upgrader code.<br>
<br>Or renaming them for backup purposes when they are auto upgraded? <br><br><br>