hdf5_ep

/* * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * *

 * Copyright by The HDF Group.                                               *

 * Copyright by the Board of Trustees of the University of Illinois.         *

 * All rights reserved.                                                      *

 *                                                                           *

 * This file is part of HDF5.  The full HDF5 copyright notice, including     *

 * terms governing use, modification, and redistribution, is contained in    *

 * the files COPYING and Copyright.html.  COPYING can be found at the root   *

 * of the source code distribution tree; Copyright.html can be found at the  *

 * root level of an installed copy of the electronic HDF5 document set and   *

 * is linked from the top-level documents page.  It can also be found at     *

 * http://hdfgroup.org/HDF5/doc/Copyright.html.  If you do not have          *

 * access to either file, you may request a copy from help@hdfgroup.org.     *

 * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * */

​

/*

 * Programmer:  Robb Matzke <matzke@llnl.gov>

 *              Wednesday, April  8, 1998

 * Modified:    Albert Cheng <acheng@hdfgroup.org>

 *      September 11, 2010

 */

/*

 * The purpose of this test is to verify if a virtual file driver can handle:

 *    a. Large file (2GB)

 *    This should exceed 32bits I/O system since offset is a signed

 *    integral type (in order to support negative offset with respect to

 *    end of file).

 *    b. Extra Large file (4GB)

 *    This definite exceeds 32bit I/O and file systems.

 *    c. Huge file (tens of GB)

 *    This verifies the HDF5 library handles big logical file size

 *    correctly.

 * In practice, if a VFD can handle a big file size, there is no need to

 * test the smaller file sizes.  E.g., If it can handle the Huge file,

 * there is no need to test the Extra large or Large files. Therefore the

 * test starts with larger size files and continues to test the smaller size

 * files only if the large sige file tests have failed.

 *

 * Another consideration is that even if a VFD is capable to handle a

 * huge file but it is likely to take a long time to write every byte

 * of a huge file. E.g., a simple workstation may have disks of write

 * speed of 10MB/sec. A huge file of 30GB will take about an hour to

 * write it. Therefore, this test will run the huge file test only if the

 * underlying file system supports sparse file. (A Sparse file here means

 * that disk space is allocated only when the contents are actually written.

 * E.g., If one creates a new file, seeks forward 10 million bytes, writes

 * 1 bytes and closes the file, then a sparse file, will show file size of

 * 10 million bytes but actaully uses only couple disk blocks, much smaller

 * than the formal file size.)

 *

 * One more consideration is that we want to distinguish an HDF5 library