1NFSTEST_FILE(1) nfstest_file 1.2 NFSTEST_FILE(1)
2
3
4
6 nfstest_file - Find all packets for a specific file
7
9 nfstest_file [options] -p <filepath> <trace1.cap> [<trace2.cap> ...]
10
12 Display all NFS packets for the specified path. It takes a relative
13 path, where it searches for each of the directory entries given in the
14 path until it gets the file handle for the directory where the file is
15 located. Once the directory file handle is found, a LOOKUP or OPEN/CRE‐
16 ATE is searched for the given file name. If the file lookup or creation
17 is found, all file handles and state ids associated with that file are
18 searched and all packets found, including their respective replies are
19 displayed.
20
21 There are three levels of verbosity in which they are specified using a
22 bitmap, where the most significant bit gives a more verbose output.
23 Verbose level 1 is used as a default where each packet is displayed
24 condensed to one line using the last layer of the packet as the main
25 output.
26
27 The packet trace files are processed either serially or in parallel.
28 The packets are displayed using their timestamps so they are always
29 displayed in the correct order even if the files given are out of
30 order. If the packet traces were captured one after the other the
31 packets are displayed serially, first the packets of the first file
32 according to their timestamps, then the second and so forth. If the
33 packet traces were captured at the same time on multiple clients the
34 packets are displayed in parallel, packets are interleaved from all the
35 files when displayed again according to their timestamps.
36
37 Note: A packet call can be displayed out of order if the call is not
38 matched by any of the file handles, state ids or names but its reply is
39 matched so its corresponding call is displayed right before the reply.
40
41
42
44 --version
45 show program's version number and exit
46
47 -h, --help
48 show this help message and exit
49
50 -p PATH, --path=PATH
51 Path relative to the mount point, the path can be specified by
52 its file handle 'FH:0xc3f001b4'. Also the relative path could
53 start with a directory file handle 'DH:0x0c35bb58/file_name'
54
55 --stid=STID
56 State id to include in the search
57
58 -v VERBOSE, --verbose=VERBOSE
59 Verbose level bitmask [default: 1]. bitmap 0x01: one line per
60 packet. bitmap 0x02: one line per layer. bitmap 0x04: real
61 verbose.
62
63 -s START, --start=START
64 Start index [default: 0]
65
66 -e END, --end=END
67 End index [default: 0]
68
69 -z TZ, --tz=TZ
70 Time zone to use to display timestamps
71
72 --progress=PROGRESS
73 Display progress bar [default: 1]
74
75
76 Packet display:
77 --frame=FRAME
78 Display record frame number [default: 0]
79
80 --index=INDEX
81 Display packet number [default: 1]
82
83 --crc16=CRC16
84 Display CRC16 encoded strings [default: True]
85
86 --crc32=CRC32
87 Display CRC32 encoded strings [default: True]
88
89 --strsize=STRSIZE
90 Truncate all strings to this size [default: 0]
91
92
93 Debug:
94 --enum-check=ENUM_CHECK
95 If set to True, enums are strictly enforced [default: False]
96
97 --debug-level=DEBUG_LEVEL
98 Set debug level messages
99
101 # Find all packets for relative path: nfstest_file -p
102 data/name_d_1/name_d_2/name_f_13 nested_dir_v3.cap
103
104 # Find all packets for relative path, starting with a directory file
105 handle: nfstest_file -p DH:0x34ac5f28/name_d_1/name_d_2/name_f_13
106 nested_dir_v3.cap
107
108 # Find all packets for file, starting with a directory file handle:
109 nfstest_file -p DH:0x0c35bb58/name_f_13 nested_dir_v3.cap
110
111 # Find all packets for file handle nfstest_file -p FH:0xc3f001b4
112 /tmp/trace.cap
113
114 # Find all packets for file, including all operations for the given
115 state id nfstest_file -p f00000001 --stid 0x0fd4 /tmp/trace.cap
116
117 # Display all packets for file (one line per layer) nfstest_file -p
118 f00000001 -v 2 /tmp/trace.cap
119
120 # Display all packets for file
121 # (real verbose, all items in each layer are displayed) nfstest_file -p
122 f00000001 -v 4 /tmp/trace.cap
123
124 # Display all packets for file (display both verbose level 1 and 2)
125 nfstest_file -p f00000001 -v 3 /tmp/trace.cap
126
127 # Display packets for file between packets 100 through 199
128 $ nfstest_file -p f00000001 -s 100 -e 200 /tmp/trace.cap
129
130 # Display all packets truncating all strings to 100 bytes
131 # This is useful when some packets are very large and there
132 # is no need to display all the data
133 $ nfstest_file -p f00000001 --strsize 100 -v 2 /tmp/trace.cap
134
135 # Display packets using India time zone
136 $ nfstest_file -p f00000001 --tz "UTC-5:30" /tmp/trace.cap
137 $ nfstest_file -p f00000001 --tz "Asia/Kolkata" /tmp/trace.cap
138
139 # Display all packets for file found in all trace files given
140 # The packets are displayed in order using their timestamps
141 $ nfstest_file -p f00000001 trace1.cap trace2.cap trace3.cap
142
144 formatstr(3), nfstest_alloc(1), nfstest_cache(1), nfstest_delega‐
145 tion(1), nfstest_dio(1), nfstest_interop(1), nfstest_io(1),
146 nfstest_lock(1), nfstest_pkt(1), nfstest_pnfs(1), nfstest_posix(1),
147 nfstest_sparse(1), nfstest_ssc(1), nfstest_xid(1),
148 packet.nfs.nfs3_const(3), packet.nfs.nfs4_const(3), packet.pktt(3),
149 packet.record(3), packet.utils(3)
150
151
153 No known bugs.
154
156 Jorge Mora (mora@netapp.com)
157
158
159
160NFStest 2.1.5 14 February 2017 NFSTEST_FILE(1)