summaryrefslogtreecommitdiffstats
path: root/tools
diff options
context:
space:
mode:
authorQuincey Koziol <koziol@hdfgroup.org>2004-02-02 03:58:29 (GMT)
committerQuincey Koziol <koziol@hdfgroup.org>2004-02-02 03:58:29 (GMT)
commit517643f146678574693ee13a4857d55c1893f02b (patch)
tree812bb367fdf38aebd024da15741ab9d943e7a16f /tools
parent233319898db1bc7e8e28c150e55c9dcc7f068d82 (diff)
downloadhdf5-517643f146678574693ee13a4857d55c1893f02b.zip
hdf5-517643f146678574693ee13a4857d55c1893f02b.tar.gz
hdf5-517643f146678574693ee13a4857d55c1893f02b.tar.bz2
[svn-r8144] Purpose:
Bug fix. Description: Revert the optimization to the MPI-I/O VFD from earlier this week that eliminated calling MPI_File_set_size() when a file was truncated. This doesn't work because of the way we track the 'eoa' (end of allocated space) in the file: we just advance the eoa value when space is allocated in the file and we don't zero out the space in the file. This causes a problem where we assume that all "newly allocated" space in the file contains zero bytes, but if we don't call MPI_File_set_size(), the file can contain the previous data (if the file previously existed) and not zeros. Unfortunately, because we allow independent raw data parallel I/O, there is no way to address this issue. :-( Solution: Revert to previous method of retrieving the file's size, etc. from before the optimization. Platforms tested: FreeBSD 4.9 (sleipnir) w/parallel too minor to require h5committest.
Diffstat (limited to 'tools')
0 files changed, 0 insertions, 0 deletions