2 # Copyright (c) 2000-2001 Silicon Graphics, Inc. All Rights Reserved.
10 A) Extracting from DMAPI_test.cpio
12 1) Create a new directory for storing the tests. We will refer to
13 this as the "base" directory. The base directory can be
14 located anywhere; it does NOT need to be in a DMAPI filesystem.
16 2) Move the archive file DMAPI_test.cpio to the base directory
17 and execute the following command to extract from the archive:
19 cat DMAPI_test.cpio | cpio -icd
21 3) There should now be several files and subdirectories in the base
22 directory, including the file "file_list". Read this file for a
23 complete listing of which files should be present in which
24 directories. Compare "file_list" with the output of "ls -Rpl"
25 to be sure that you have the necessary files.
27 4) The base directory contains the files and programs that are of
28 immediate use for testing. The "bindir" subdirectory contains
29 the test programs and datafiles. The "lib" and "src" subdirectories
30 contain C libraries and source code for the C programs.
32 B) Checking the Existence and Version of DMAPI
34 The program check_dmapi can verify that you have the correct
35 version of DMAPI installed. Note: it can only be run as root.
36 Execute this command (from the "base" directory):
40 It should report that you have a current version of DMAPI. If it
41 does not, it will also suggest which components of your DMAPI are
42 not current, and where to find a patch to update them.
46 1) Creating the Test Directories
48 a) The Test Filesystem
50 Mount a DMAPI filesystem, or use an existing one.
51 This filesystem's mount info MUST be listed in /etc/fstab.
53 Write down the path to this filesystem's mountpoint, and label
54 it as "m_main" for future use.
56 b) The Main Test Directory
58 Create a new directory in the "m_main" filesystem.
60 Write down the path to this directory. Note ONLY the part
61 that comes AFTER "m_main". Label this as "d_name".
63 EXAMPLE: You have a DMAPI filesystem /dmi_main
64 You name the test directory /dmi_main/test_dir
68 c) The Cross-NFS Test Directories
70 For NFS tests, all you must do is create two empty directories
71 (one for nfs2, one for nfs3). They do NOT need to be in a
74 Your main test directory will be mounted across NFS, into these
75 two directories. Normally, the tests will do this automatically.
76 However, if you need to do this mount manually, the command
77 would look like this example:
79 mount -t nfs2 localhost:/dmi_main /dmi_nfs2
81 Write down the paths to these nfs2 and nfs3 test directories.
82 Label them "m_nfs2" and "m_nfs3" respectively.
84 c) The Realtime Test Filesystem and Directory
86 If you wish to test realtime i/o, you'll need a filesystem
87 mounted with a realtime partition, and a directory in that
90 Label the path to the filesystem mountpoint as "m_rt".
91 Label the path to the test directory as "d_rt".
93 2) Configuring menu_test
95 The Korn-shell script named menu_test is an interface to the
96 other test programs. At the beginning of the script, there
97 is a "configuration section", in which is sets several variables
98 for use in the rest of the script.
100 Open menu_test in any text editor and change the following
101 variable assignments in the configuration section:
104 Set this to the pathname of your "base" directory
105 (where you un-archived "DMAPI_test.cpio").
108 Tests that do not run as root will run as this "primary" user.
109 Set this to any username.
112 The mountpoint of the main test filesystem.
113 Set this to the value of "m_main" that you wrote down above.
116 m_main concatenated with d_name is the main test directory path.
117 Set this to the value for "d_name" that you wrote down above.
120 The mountpoint of the nfs2 test filesystem.
121 Set this to the value of "m_nfs2" that you wrote down above.
124 The mountpoint of the nfs3 test filesystem.
125 Set this to the value of "m_nfs3" that you wrote down above.
128 The mountpoint of the realtime test filesystem.
129 Set this to the value of "m_rt" that you wrote down above.
132 The path to the realtime test directory.
133 Set this to the value of "d_rt" that you wrote down above.
135 3) Configuring "DMAPI_aliases"
137 This is an optional alternative to the menu interface. It runs
138 as a Korn shell "dot" script and creates an alias to each test.
139 It was made for those who wish to run tests directly from the
142 DMAPI_aliases has exactly the same configuration section as
143 menu_test. If you wish to use DMAPI_aliases, make the same
144 changes to its configuration section.
146 II) Running the Tests
148 A) Using "menu_test" to run tests
150 1) You must be superuser, using the Korn shell, to run menu_test.
151 You also must have adjusted the variables in menu_test's
152 "configuration section", as was explained above.
154 2) menu_test is (surprise!) menu based. Choose options by entering
157 3) The names of the menu options explain which DMAPI functions
158 or DMAPI events are being tested. Some of the options, labeled
159 accordingly, run more than one test programs.
161 4) See section SECTION# for a list of the test scripts and programs,
162 and a brief explanation of each script or program's function.
164 B) Using "DMAPI_aliases" to run tests
166 1) NOTE: The aliases in DMAPI_aliases are meant to be used by
167 those who are familiar with the test programs and wish to run
168 them more directly. [Designer's note: I included the alias
169 file more out of nostalgia than necessity.]
171 2) You should be superuser, using the Korn shell, to run DMAPI_aliases.
172 You also must have adjusted the variables in DMAPI_aliases's
173 "configuration section", as was explained above.
175 3) DMAPI_aliases should be invoked as a Korn shell "dot" script:
179 It sets an alias for each test program; each alias begins with
180 the characters "do_" and is followed by some appropriate name.
181 Read DMAPI_aliases, or execute "alias | grep do", to
183 C) Running tests directly
185 1) For the VERY adventurous, all the tests in the "bindir" directory
186 can be run directly from the command line. Only some of the files
187 in "bindir" are test scripts/programs. Read section III for a list
188 of function tests and section IV for a list of run_test (.dat)
191 2) Running a test program without parameters will produce a list of
192 correct options. (The exception to this is check_dmapi, which
193 normally has no parameters. check_dmapi takes only one option,
194 [-v] for verbose output.)
196 3) It is suggested that you read a program's source before running
197 it directly. (The source of the C programs is included in the
198 "src" directory.) Specificually, in each source file, an initial
199 comment explains the program's options/parameters in detail.
201 III) DMAPI Function tests:
203 This section offers a terse description of the DMAPI function tests.
204 For those tests written in C, the source code is given in the "src"
205 directory. The ksh scripts can, of course, be read directly.
206 In all cases except check_dmapi, running the program without
207 parameters will produce a list of correct options.
211 Test of: presence (and correct version) of DMAPI library and kernel.
212 Options: [-v] flag for verbose output.
216 Test of: dm_get_dmattr, dm_set_dmattr, dm_remove_dmattr.
220 Test of: various bad function calls that should generate EFAULT,
221 according to the DMAPI specification.
225 Test of: dm_get_eventlist, dm_set_eventlist.
229 Test of: dm_get_fileattr, dm_set_fileattr,
230 dm_get_dirattrs, dm_get_bulkattr.
234 Test of: dm_probe_hole, dm_punch_hole.
238 Test of: dm_read_invis, dm_write_invis.
242 Test of: dm_get_region, dm_set,region.
246 Test of: various bad function calls that should generate EACCES,
247 and other conditions pertaining to DMAPI rights.
251 Test of: dm_get_allocinfo.
255 Test of: dm_get_allocinfo.
257 IV) DMAPI Event tests and the "run_test" ksh script
259 A) How to use the "run_test" script
261 1) A quick description of run_test's behavior:
262 run_test invokes a DMAPI daemon (as a ksh coprocess). It then
263 reads a "testfile", which contains a description of the test.
265 2) You must be superuser, using the Korn shell, to execute run_test.
267 3) Executing run_test without parameters will produce a list of
268 correct options. For a much more in-depth explanation of the
269 options to run_test, read its own initial comment.
271 B) The existing .dat testfiles
284 C) How to write ".dat" testfiles
288 A testfile contains a complete description of a DMAPI event test.
289 Testfiles are divided into sections: the first two contain
290 test initialization, while the remaining sections each contain ONE
291 command, followed by a list of expected events.
293 The following is a description of testfile syntax. If you wish to
294 fully understand testfile syntax, PLEASE examine the existing
295 testfiles and the "run_test" script.
297 2) Event information variables
299 a) From the daemon, "run_test" gets information about DMAPI events.
300 This information is stored in event information variables.
302 b) NOTE: event information variables are not persistant.
303 After "run_test" has compared the expected and actual events
304 for a command, and before it executes the next command, it
305 unsets the values of all these variables.
307 c) Most of these variables are arrays, indexed by the number of
308 the event (starting with 0). For example, if the initial event
309 is a read event, then we have "event[0]" set to "read", and
310 "file_handle[0]" set to the handle of whatever file was read.
312 d) "event_count" is a special variable. It holds the number of
313 events that were generated by the most recent command.
315 e) These are all the event information variables:
317 contents event event_count fs_handle handle length
318 offset media_designator mode mountpoint_handle
319 mountpoint_path msg_str name new_name new_parent
320 parent_handle ret_code root_handle sequence token
321 tries_left unmount_mode
323 f) PLEASE examine the run_test script to see which variables
324 are set by which events. (The scheme corresponds, roughly,
325 to the "Event Types" section of the DMAPI specification.)
327 3) Testfile section 1: List of required files
329 a) A testfile's first section is a list of the files it requires.
330 If these files are not present in the "bindir" directory,
331 "run_test" will abort the test and inform the user of which
334 b) Each line of this section may contain ANY NUMBER of filenames.
336 c) Lines beginning with // will be treated as comments. The
337 entirety of such lines will be ignored.
339 d) The last line of this section should begin with three hyphens
340 --- Other characters on that line will be ignored.
342 4) Testfile section 2: Initialization commands
344 a) A testfile's second section consists of a list of commands.
345 "run_test" will execute these commands before starting the
346 DMAPI daemon. Any necessary initialization should be done
349 b) Each line of this section should be ONE shell command.
351 c) Lines beginning with // will be treated as comments.
352 The entirety of such lines will be ignored.
354 d) The last line of this section should begin with three hyphens
355 "---" Other characters on that line will be ignored.
357 5) Testfile sections 3 and on: Individual tests
359 a) The remaining sections of a testfile consist of a single
360 shell command, followed by descriptions of events that should
361 be generated by the command.
365 1) Comments are valid ONLY before the command.
367 2) Lines beginning with // will be treated as comments.
368 The entirety of such lines will be ignored.
370 3) Lines beginning with @@ will be treated as "print" comments.
371 Such lines will not be parsed, but they will be printed to
372 standard output during the test. This is useful for
373 describing what each test does.
375 c) Valid grammar for the command itself
377 1) Standard command syntax:
378 This should be ONE shell command, on a line by itself.
380 2) Alternate command syntax:
383 If the test is preceeded by the metacommand "run_as_root"
384 (on a line by itself) then the command will be run as
385 root rather than as "p_user". The command should still
386 be one command on a line by itself.
389 If the test is preceeded by the metacommand
390 "run_without_test" (on a line by itself), then ALL
391 subsequent lines in the section will be executed as
392 commands, and NO testing will be performed. Note that
393 the commands will be executed as root. This is useful
394 for re-initialization sections during a test.
396 d) Valid grammar for the "expected events" lines
398 1) [variable_name] [value]
399 This specifies that the variable [variable_name] should be
402 2) [variable_name_1] matches [variable_name_2]
403 This specifies that both variables should be set to
404 the same value. A list of valid variables
406 3) [variable_name] store_in [string]
407 This specifies that the contents of [variable_name]
408 should be stored in a variable named [string].
409 The variable [string] can then be referenced as a
410 variable in later tests.
412 EXAMPLE: if two commands deal with the file "foobar",
413 you might want to check that they both use the same handle.
414 In the first section, write
415 "handle[0] store_in old_handle_0"
416 In the second section, write
417 "old_handle_0 matches handle[0]"
420 This specifies that the command is expected to fail
421 (return some non-zero exit status). If "failure"
422 is not specified, the command is expected to succeed.
424 e) The last line of these sections should begin with three
425 hyphens "---". Other characters on that line will be ignored.
427 6) Sending messages to the DMAPI daemon
430 7) Other "helper functions" for testfiles