Appendix A. dump Option Output
Prev   Next

Appendix A. dump Option Output

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.

ufile_data

The following is an example of ufile_data output:

ufile_data|345612ca0000000000000001|
010000000000001885beb4c83ff373e0000e00000000001b0000000000000048|0|4474283|1|2|0

Table A-1. ufile_data Output

Field

Description

1

ufile_data

2

Bitfile ID (BFID)

3

File handle (fhandle)

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)
7 (missing file; just a place-holder)

8

Name list offset. A 0 (zero) indicates that the names of the file are not known; a nonzero value indicates that the names are known.


ufile_name

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

Table A-2. ufile_name Output

Field

Description

1

ufile_name

2

BFID

3

Path name: unprintable characters expanded


ufile_error

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/VG daemon database entries 
exist for this user file.

Table A-3. ufile_error Output

Field

Description

1

ufile_error

2

BFID

3

Error message text


ufile_action

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.

Table A-4. ufile_action Output

Field

Description

1

ufile_action

2

BFID

3

Action message text


mdmdb_data

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

Table A-5. mbmdb_data Output

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


mdmdb_error

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.

Table A-6. mdmdb_error Output

Field

Description

1

mdmdb_error

2

BFID

3

Error message text


mdmdb_action

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.

Table A-7. mdmdb_action Output

Field

Description

0

mdmdb_action

1

BFID

2

Action message text


Prev Table of Contents Next
Chapter 8. Changing the Configuration  Glossary