Re: Recovering badly closed file?

Hi Philippe,

Philippe Canal <pcanal_at_fnal.gov> writes:

> Do you get the same error with 'BeamMon;2161' (which is a priori newer
> than ;1) ?

The ";1" only shows up after I do a Recover(). Browsing ";1" leads to a segmentation fault the other to a "std:bad_alloc" exception.

However! Going back and checking on your question I noticed an error that I missed before:

  Warning in <TBufferFile::CheckByteCount>: TBranch::Streamer() not in   sync with data on file /home/bviren/B100112_080001.mbeam.root, fix   Streamer()

This made me suspect version shear. Indeed I was testing the file using an older release of ROOT and our own code than was used to produce the file. Using the same versions as was used to produce the file lets me to a TTree::Scan() and it looks like the majority of the data is recoverable!

Thanks for the nudge in the right direction, -Brett. Received on Wed Jan 20 2010 - 23:43:31 CET