No luck reproducing it in something simple so far. The code has ~15 data
sets that are written to a mixed manner through a wrapper and I haven't
managed to get bad behavior (other than something I'll post in a separate
email) with direct usage.
On Tue, May 15, 2012 at 11:40 AM, Quincey Koziol [via hdf-forum] <
[email protected]> wrote:
> Hi Daniel,
> Hmm, can you pin this down to a small sample program that you could send
> us?
>
> Quincey
>
> On May 10, 2012, at 11:30 AM, Daniel Russel wrote:
>
> ext4 and hfs+, nothing too exotic, I'm afraid.
>
> On Wed, May 9, 2012 at 10:29 PM, Salnikov, Andrei A. <[hidden
> email]<http://user/SendEmail.jtp?type=node&node=3988636&i=0>
> > wrote:
>
>> Hi Drussel,
>>
>> what filesystem are you writing to? We had bad case of non-reproducible
>> metadata corruption when writing HDF5 to older version of Lustre.
>>
>> Cheers,
>> Andy.
>>
>> [hidden email] <http://user/SendEmail.jtp?type=node&node=3988636&i=1>wrote
>> on 2012-05-08:
>>
>> > Having investigated further, the problem is not actually connected to
>> > reopening of HDF5 files, and occurs, intermittently, even when I don't
>> > reopen the file and instead just re-write the entries in the data sets.
>> > I have made a build of HDF5 with its internal memory management turned
>> > off (on a different machine), and run the whole thing through with
>> > valgrind. Valgrind reports no errors (nor does hdf5), but the resulting
>> > files are (sometimes) reported as having errors when accessed afterwards
>> > either by our code or tools like h5dump.
>> >
>> > Any suggestions as to what to try next? We have numerous various simple
>> > tests of our code that don't exhibit the problem and, so far, my
>> > attempts to produce a simpler example have not yielding something
>> > useful. Thanks very much.
>> >
>>
>>
>>
>> _______________________________________________
>> Hdf-forum is for HDF software users discussion.
>> [hidden email] <http://user/SendEmail.jtp?type=node&node=3988636&i=2>
>> http://mail.hdfgroup.org/mailman/listinfo/hdf-forum_hdfgroup.org
>>
>
> _______________________________________________
> Hdf-forum is for HDF software users discussion.
> [hidden email] <http://user/SendEmail.jtp?type=node&node=3988636&i=3>
> http://mail.hdfgroup.org/mailman/listinfo/hdf-forum_hdfgroup.org
>
>
>
> _______________________________________________
> Hdf-forum is for HDF software users discussion.
> [hidden email] <http://user/SendEmail.jtp?type=node&node=3988636&i=4>
> http://mail.hdfgroup.org/mailman/listinfo/hdf-forum_hdfgroup.org
>
>
> ------------------------------
> If you reply to this email, your message will be added to the discussion
> below:
>
> http://hdf-forum.184993.n3.nabble.com/reopening-for-writing-after-close-tp3942092p3988636.html
> To unsubscribe from reopening for writing after close, click
> here<http://hdf-forum.184993.n3.nabble.com/template/NamlServlet.jtp?macro=unsubscribe_by_code&node=3942092&code=ZHJ1c3NlbEBnbWFpbC5jb218Mzk0MjA5Mnw2MDMzODI3ODE=>
> .
> NAML<http://hdf-forum.184993.n3.nabble.com/template/NamlServlet.jtp?macro=macro_viewer&id=instant_html%21nabble%3Aemail.naml&base=nabble.naml.namespaces.BasicNamespace-nabble.view.web.template.NabbleNamespace-nabble.view.web.template.NodeNamespace&breadcrumbs=notify_subscribers%21nabble%3Aemail.naml-instant_emails%21nabble%3Aemail.naml-send_instant_email%21nabble%3Aemail.naml>
>
--
View this message in context:
http://hdf-forum.184993.n3.nabble.com/reopening-for-writing-after-close-tp3942092p3998102.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
