This repository has been archived by the owner on Nov 30, 2017. It is now read-only.
-
Notifications
You must be signed in to change notification settings - Fork 16
/
RELEASE_LOG
executable file
·146 lines (124 loc) · 6.96 KB
/
RELEASE_LOG
1
2
3
4
5
6
7
8
9
10
11
12
13
14
15
16
17
18
19
20
21
22
23
24
25
26
27
28
29
30
31
32
33
34
35
36
37
38
39
40
41
42
43
44
45
46
47
48
49
50
51
52
53
54
55
56
57
58
59
60
61
62
63
64
65
66
67
68
69
70
71
72
73
74
75
76
77
78
79
80
81
82
83
84
85
86
87
88
89
90
91
92
93
94
95
96
97
98
99
100
101
102
103
104
105
106
107
108
109
110
111
112
113
114
115
116
117
118
119
120
121
122
123
124
125
126
127
128
129
130
131
132
133
134
135
136
137
138
139
140
141
142
143
144
145
146
Changes in mdtest-1.9.3
* Checked for -B used with -N. This creates possible race conditions where
a process may try to stat or delete a file it did not create and the
process responsible did not yet create it or another process already
deleted it (in the case of stat).
Changes in mdtest-1.9.2
* Updated PLFS support to PLFS 2.5 API calls that return plfs_error_t. This
means that mdtest 1.9.2 is not compatible with PLFS versions prior to 2.5.
Changes in mdtest-1.9.1
* Removed duplicate . files from directories.
* Fixed shared file (-S) output to state 1 file not file count based on
process count.
Changes in mdtest-1.9
* Added use of PLFS library calls. So, a target of I/O testing can be a
PLFS file system.
To control whether or not mdtest is built with PLFS, one needs something
like the following cshrc code segment:
#
# If we're not going to use PLFS with mdtest, we don't need to define this variable.
#
# setenv MDTEST_FLAGS ""
#
# If we're going to use PLFS with mdtest, we need to define this variable based on
# whether we are loading a PLFS module or using the system default PLFS installation.
#
if ( $?PLFS_CFLAGS ) then
setenv MDTEST_FLAGS "-D_HAS_PLFS ${PLFS_CFLAGS} ${PLFS_LDFLAGS}"
else
setenv MDTEST_FLAGS "-D_HAS_PLFS -I${MPICH_DIR}/include -lplfs"
endif
* Changed the item count variables to be unsigned long long so that a
test can be run with more than 2^31-1 (max value of int) items.
* Fixed the remove process so that all of the directories that mdtest
creates get deleted if the remove flag is set. Before the #test.0
class of directories remained with no files in them.
Changes in mdtest-1.8.4
* Added read option to extend create (write) capability. New feature will:
-E: Only perform the read phase of the tests.
-e #: Set the number of Bytes to read from each file.
Fixes in mdtest-1.8.3
* Prepared for release on sourceforge.net
Fixes in mdtest-1.8.2
* With the new changes issued in mdtest-1.8.0, all files and directories
were operated upon by using the full path to each file/dir. Full paths
are no longer used. Now a relative path is used from the root dir of
each directory tree.
* fixed bug in collective creates and unique directory per task mode
Fixes in mdtest-1.8.1
* A new test directory is created for each iteration. Then for each
iteration the directory structure is created/removed. This allowed
multiple iterations of the create-only mode. The name of the test
directories has changed as a result of this fix. Also, aggregate
creation/removal times are computed now over the number of iterations.
Changes in mdtest-1.8.0
* added option to create files/dirs in tree-like directory structure:
Previously, all files/dirs were created in one test directory. Now the
root directories of the tree(s) are created in that test directory.
Files/dirs are then created within those root directories or their children.
If the -u flag is specified, then unique trees are created per proc.
Otherwise, one tree is created. This coincides with the previous
functionality. The following flags were added/changed to incorporate this
new feature:
-z #: Indicates the depth of the leaves of the tree. If this flag is not
specified, the depth defaults to 0 (i.e. files/dirs are created in
the top-level directories).
-b #: Indicates the branching factor of the tree. If this flag is not
specified, the branching factor defaults to 1. Branching factor
indicates the number of children that each non-leaf node has.
-L: Indicates that files/dirs should only be created at the leaf level
of the tree.
-I #: Indicates the number of files/dirs that should be created within
each directory of the tree.
-n #: This flag still indicates the total number of files/dirs that should
be created. However, with the new tree structure some calculations
are done to determine the number of files that should be created per
directory in the tree. Due to rounding the actual total number of
files may differ slightly from what is specified.
* added option to choose which phases to run:
The create, stat, and remove phases of mdtest have been separated. There
are flags now that allow the user to choose which phases they want to
perform. If none of these flags is specified, then the default usage is
to do all of the phases. The user is trusted to be intelligent about their
choice of phases. As a result of the separation of the phases, the naming
convention of the files/dirs had to be altered slightly.
* added option to not barrier between each phase (create/stat/remove):
A major change in mdtest is the ability to time each proc that is running
the different phases of mdtest. The default functionality is the same as
the previous version - barriers are taken between phases (create/stat/
remove). Also, in the default case, the resultant times reflect the
slowest rates for each phase. If the -B flag is specified, then no barriers
are taken between the phases. There is a race condition when specifying
this flag, but it is rarely met. The race condition is that one proc might
be trying to remove a file in the shared file case before someone else has
a chance to stat the file. Also, when the -B flag is specified, the
resultant rates are aggregates over the number of iterations and the number
of procs used. The default case, as mentioned above, calculates aggregates
only over the number of iterations where the time for each phase of an
iteration is the time of the slowest proc for that particular phase.
* added option to stat files/dirs in a random order:
The default usage of mdtest will stat files in sequential order. Now,
however, items can be stat'ed in a random order by specifying the -R flag.
Even though the stat order is random with this usage, items are still only
stat'ed once each. This is achieved by randomly sorting a list of unique
item IDs before running the different tests. A seed for the random number
generator can optionally be provided with the following syntax: -R#.
Fixes in mdtest-1.7.5
* changed bug in how test directory was created (race condition)
* added multipath option for test directories ('-d path1@path2@path3')
* added man page and correct malloc error-checking (patches from Jim Garlick)
Fixes in mdtest-1.7.4:
* folded b_remove_0 branch into main HEAD branch
Fixes in mdtest-b_remove_0:
* added remove option to only remove files from previous run
Fixes in mdtest-pre_b_remove_0:
* simple clean up for preparing for branch
Fixes in mdtest-1.7.3:
* added statfs() to get file system data block and inode usage, replacing
system() call
Fixes in mdtest-1.7.2:
* initialized declared variables
* modified df disk usage call
* added error-checking for chdir()
Fixes in mdtest-1.7.1:
* added '-y' option to sync file after write