Menu
▾
▴
Re: [gridsam-discuss] GridSAM file staging errors
|
From: Stefan Z. <ste...@uc...> - 2009-10-05 14:02:22
|
Hi Justin, On 2 Oct 2009, at 10:19, Justin Bradley wrote: > Hi Stefan, > > This is not a problem I've seen before. I have a few questions... > Which version of GridSAM is this with? Sorry, I should have said: it's GridSAM 2.0.2 in OMII 3.4 > And what type of WebDAV server is this (tomcat's, httpd apache's)? I've tried with both Tomcat and Apache, and the same thing happens. > Is there a way to see if the corrupted files have been truncated > rather than transcoded (are the corrupted ones smaller, and have > they been turned from 'data' to 'text')? > The corrupted ones are larger. For text files it seems that a byte is added for each line of the file - it looks like DOS style carriage returns are being automatically added for each file. The original file on the NGS machine: $ file alanin.xsc alanin.xsc: ASCII text The file that has been staged to WebDav by GridSAM: $ file alanin.xsc alanin.xsc: ASCII text, with CRLF line terminators Extra bytes are also being added to the binary files that are staged back, but I'm not sure what they are. Thanks, Stefan. > Justin > > On 2 Oct 2009, at 10:10, Stefan Zasada wrote: > >> Hi, >> >> We have GridSAM instances setup to submit jobs to the UK NGS via >> the Globus GRAM 2 connector. When running our jobs, we use GridSAM >> to stage input and output data from a WebDav server to the GridFTP >> server running on the NGS node we are using. While there are no >> problems staging files from our WebDav server to the NGS, when we >> stage data back we see that some of the files have been mangled. >> All files staged back to the WebDav server after the job completes >> are of different sizes and have different MD5 signatures to the >> original versions on the NGS node, for example: >> >> NGS >> [ngs0009@vidar 154382481094266025861]$ md5sum fbpc-1-a-3.out.dcd >> ba25432f11942ab81d325796dbfc7003 fbpc-1-a-3.out.dcd >> >> Local machine >> nak 585 $ md5 fbpc-1-a-3.out.dcd >> MD5 (fbpc-1-a-3.out.dcd) = f6ecc06a87df9cd559519de4ea467bbc >> >> >> Has anyone come across this problem before? We are using GridSAM >> with OMII container >> >> Any help resolving this would be much appreciated. >> >> Thanks, >> >> Stefan. >> ------------------------------------------------------------------------------ >> Come build with us! The BlackBerry® Developer Conference in SF, >> CA >> is the only developer event you need to attend this year. Jumpstart >> your >> developing skills, take BlackBerry mobile applications to market >> and stay >> ahead of the curve. Join us from November 9-12, 2009. Register >> now! >> http://p.sf.net/sfu/devconf_______________________________________________ >> GridSAM-Discuss mailing list >> Gri...@li... >> https://lists.sourceforge.net/lists/listinfo/gridsam-discuss > > -- > Justin Bradley > Design & Development Team Leader > j.b...@om... > OMII-UK > Bay 23, 4067, B32 > University of Southampton > > > > > ------------------------------------------------------------------------------ > Come build with us! The BlackBerry® Developer Conference in SF, CA > is the only developer event you need to attend this year. Jumpstart > your > developing skills, take BlackBerry mobile applications to market and > stay > ahead of the curve. Join us from November 9-12, 2009. Register > now! > http://p.sf.net/sfu/devconf_______________________________________________ > GridSAM-Discuss mailing list > Gri...@li... > https://lists.sourceforge.net/lists/listinfo/gridsam-discuss |
