This appendix describes the fields that appear in the dmaudit command dump option output. dmaudit dumps information about a bfid set as a series of consecutive lines. The bfid is the second field. The first field of each line details the type of data that line contains.
Each type of output produced by dmaudit is shown. An example of each is given, and each field within a line is described. dmaudit prints each of the data records defined below as one long line. However, long lines in the examples have been broken into multiple lines for readability.
The following is an example of ufile_data output:
ufile_data|345612ca0000000000000001| 010000000000001885beb4c83ff373e0000e00000000001b0000000000000048|0|4474283|1|2|0 |
Field | Description |
|---|---|
1 | ufile_data |
2 | Bitfile ID (bfid) |
3 | Fhandle number |
4 | File user ID |
5 | File size (in bytes) |
6 | File link count |
7 | File state. Valid values are 0 (a regular file that has data but no bfid), 2 (a dual-state file that has data and a bfid, 3 (an offline file that has no data but has a bfid), 5 (file is exempt from migration), and 6 (missing file; just a place-holder). |
8 | Name list offset. A zero indicates that the names of the file are not known; a nonzero value indicates that the names are known. |
If present, these lines immediately follow the ufile_data line to which they apply. There is one line for each path name to a file. Backslash, vertical bar, and nonprintable characters are expanded using the format \000, where 000 is the 3-digit octal ASCII value for that character.
The following is an example of ufile_name output:
ufile_name|345612ca0000000000000001|/mig/bar |
Field | Description |
|---|---|
1 | ufile_name |
2 | Bfid |
3 | Path name: unprintable characters expanded |
If present, these lines follow the ufile_data line to which they apply. The following is an example of ufile_error output:
ufile_error|345612ca0000000000000001|No MSP daemon database entries exist for this user file. |
If present, these lines follow the ufile_data line to which they apply. The following is an example of ufile_action output:
ufile_action|345612ca0000000000000001|The bitfile ID will be removed from this user file. |
The following is an example of mdmdb_data output:
mdmdb_data|345612ca0000000000000001|33554464|67|4474272|Dec 4 10:11:01 1997| Dec 4 10:11:01 1997|Dec 4 10:11:01 1997|0|0|foo|ftp1|root/345612ca0000000000000001 |
Field | Description |
|---|---|
1 | mbmbd_data |
2 | Bfid |
3 | origdv |
4 | origino |
5 | origsz |
6 | otime |
7 | utime |
8 | ctime |
9 | delflag |
10 | userid |
11 | ofilenm |
12 | proc |
13 | path |
If present, these lines follow the mdmdb_data line to which they apply. The following is an example of mdmdb_error output:
mdmdb_error|345612ca0000000000000001|This database entry should not be soft deleted. |
If present, these lines follow the mdmdb_data line to which they apply. The following is an example of mdmdb_action output:
mdmdb_action|345612ca0000000000000001|The soft delete flag will be cleared from this entry. |