Hi!
Can you create a small test program that shows this behavior and send
it to: [email protected]? We can see what's going on then...
Quincey
On Apr 26, 2012, at 1:11 PM, [email protected] wrote:
> I was running in to trouble where I was
> - opening an hdf5 file with H5Fcreate with H5F_ACC_TRUNC
> - writing some data
> - closing it (calling flush and and making sure there were no open hdf5
> handles)
> - and then reopening it with another call to H5Fcreate and H5F_ACC_TRUNC to
> write over the file.
>
> This was resulting in corrupt hdf5 files (the various h5 tools would spit
> out errors accessing the file). If I don't close and reopen it, the file
> looked to be ok.
>
> Is this something expected? Or a result of misuse of some kind? Thanks.
>
> I got this with various hdf5 versions in the 1.8 series.
>
> --
> View this message in context:
> http://hdf-forum.184993.n3.nabble.com/reopening-for-writing-after-close-tp3942092p3942092.html
> Sent from the hdf-forum mailing list archive at Nabble.com.
>
> _______________________________________________
> Hdf-forum is for HDF software users discussion.
> [email protected]
> http://mail.hdfgroup.org/mailman/listinfo/hdf-forum_hdfgroup.org
_______________________________________________
Hdf-forum is for HDF software users discussion.
[email protected]
http://mail.hdfgroup.org/mailman/listinfo/hdf-forum_hdfgroup.org
