The application I use, StoRM[1] can store checksums on disk in an
extended user attribute - and use that to ensure the integrity of files
on disk. The algorithm currently used is adler32. The intention is to
perform end to end checksumming from file creation through storage,
transfer over the WAN
Hello,
We have switched our training class to a new venue in downtown SLC.
Springhill Suites Salt Lake City Downtown
625 South 300 West . Salt Lake City, Utah 84101 USA
Dates remain the same - June 14-16th.
**The Early Bird special for the $2295 expires on June 1st - reserve
Christopher J.Walker wrote:
The application I use, StoRM[1] can store checksums on disk in an
extended user attribute - and use that to ensure the integrity of files
on disk. The algorithm currently used is adler32. The intention is to
perform end to end checksumming from file creation through
1.6.6 gave us lots of problems. We are using 1.8.4 here. Has better
tools, for one thing, eg, lfs_migrate.
bob
On 5/24/2011 7:37 PM, Mag Gam wrote:
stick with 1.6.6 , its a great release! BTW, why did you decide to
upgrade to 1.8.x? is there a feature you are looking for?
On Fri, May 20,
Hello!
On May 25, 2011, at 6:26 AM, Christopher J.Walker wrote:
The application I use, StoRM[1] can store checksums on disk in an
extended user attribute - and use that to ensure the integrity of files
on disk. The algorithm currently used is adler32. The intention is to
perform end to end
