3 fileserver - Initializes the File Server component of the fs process
10 B<fileserver> S<<< [B<-auditlog> <I<path to log file>>] >>>
11 S<<< [B<-audit-interface> (file | sysvmq)] >>>
12 S<<< [B<-d> <I<debug level>>] >>>
13 S<<< [B<-p> <I<number of processes>>] >>>
14 S<<< [B<-spare> <I<number of spare blocks>>] >>>
15 S<<< [B<-pctspare> <I<percentage spare>>] >>>
16 S<<< [B<-b> <I<buffers>>] >>>
17 S<<< [B<-l> <I<large vnodes>>] >>>
18 S<<< [B<-s> <I<small vnodes>>] >>>
19 S<<< [B<-vc> <I<volume cachesize>>] >>>
20 S<<< [B<-w> <I<call back wait interval>>] >>>
21 S<<< [B<-cb> <I<number of call backs>>] >>>
24 S<<< [B<-implicit> <I<admin mode bits: rlidwka>>] >>>
25 S<<< [B<-readonly>] >>>
26 S<<< [B<-hr> <I<number of hours between refreshing the host cps>>] >>>
27 S<<< [B<-busyat> <I<< redirect clients when queue > n >>>] >>>
29 S<<< [B<-rxpck> <I<number of rx extra packets>>] >>>
32 S<<< [B<-rxmaxmtu> <I<bytes>>] >>>
36 S<<< [B<-allow-dotted-principals>] >>>
39 S<<< [B<-k> <I<stack size>>] >>>
40 S<<< [B<-realm> <I<Kerberos realm name>>] >>>
41 S<<< [B<-udpsize> <I<size of socket buffer in bytes>>] >>>
42 S<<< [B<-sendsize> <I<size of send buffer in bytes>>] >>>
43 S<<< [B<-abortthreshold> <I<abort threshold>>] >>>
44 S<<< [B<-enable_peer_stats>] >>>
45 S<<< [B<-enable_process_stats>] >>>
46 S<<< [B<-syslog> [<I< loglevel >>]] >>>
47 S<<< [B<-mrafslogs>] >>>
48 S<<< [B<-saneacls>] >>>
50 S<<< [B<-fs-state-dont-save>] >>>
51 S<<< [B<-fs-state-dont-restore>] >>>
52 S<<< [B<-fs-state-verify>] (none | save | restore | both)] >>>
53 S<<< [B<-vhashsize> <I<log(2) of number of volume hash buckets>>] >>>
54 S<<< [B<-vlrudisable>] >>>
55 S<<< [B<-vlruthresh> <I<minutes before eligibility for soft detach>>] >>>
56 S<<< [B<-vlruinterval> <I<seconds between VLRU scans>>] >>>
57 S<<< [B<-vlrumax> <I<max volumes to soft detach in one VLRU scan>>] >>>
58 S<<< [B<-vattachpar> <I<number of volume attach threads>>] >>>
59 S<<< [B<-m> <I<min percentage spare in partition>>] >>>
67 The B<fileserver> command initializes the File Server component of the
68 C<fs> process. In the conventional configuration, its binary file is
69 located in the F</usr/afs/bin> directory on a file server machine.
71 The B<fileserver> command is not normally issued at the command shell
72 prompt, but rather placed into a database server machine's
73 F</usr/afs/local/BosConfig> file with the B<bos create> command. If it is
74 ever issued at the command shell prompt, the issuer must be logged onto a
75 file server machine as the local superuser C<root>.
77 The File Server creates the F</usr/afs/logs/FileLog> log file as it
78 initializes, if the file does not already exist. It does not write a
79 detailed trace by default, but the B<-d> option may be used to
80 increase the amount of detail. Use the B<bos getlog> command to
81 display the contents of the log file.
83 The command's arguments enable the administrator to control many aspects
84 of the File Server's performance, as detailed in L<OPTIONS>. By default
85 the B<fileserver> command sets values for many arguments that are suitable
86 for a medium-sized file server machine. To set values suitable for a small
87 or large file server machine, use the B<-S> or B<-L> flag
88 respectively. The following list describes the parameters and
89 corresponding argument for which the B<fileserver> command sets default
90 values, and the table below summarizes the setting for each of the three
97 The maximum number of lightweight processes (LWPs) or pthreads
98 the File Server uses to handle requests for data; corresponds to the
99 B<-p> argument. The File Server always uses a minimum of 32 KB of
100 memory for these processes.
104 The maximum number of directory blocks the File Server caches in memory;
105 corresponds to the B<-b> argument. Each cached directory block (buffer)
106 consumes 2,092 bytes of memory.
110 The maximum number of large vnodes the File Server caches in memory for
111 tracking directory elements; corresponds to the B<-l> argument. Each large
112 vnode consumes 292 bytes of memory.
116 The maximum number of small vnodes the File Server caches in memory for
117 tracking file elements; corresponds to the B<-s> argument. Each small
118 vnode consumes 100 bytes of memory.
122 The maximum volume cache size, which determines how many volumes the File
123 Server can cache in memory before having to retrieve data from disk;
124 corresponds to the B<-vc> argument.
128 The maximum number of callback structures the File Server caches in
129 memory; corresponds to the B<-cb> argument. Each callback structure
130 consumes 16 bytes of memory.
134 The maximum number of Rx packets the File Server uses; corresponds to the
135 B<-rxpck> argument. Each packet consumes 1544 bytes of memory.
139 The default values are:
141 Parameter (Argument) Small (-S) Medium Large (-L)
142 ---------------------------------------------------------------------
143 Number of LWPs (-p) 6 9 128
144 Number of cached dir blocks (-b) 70 90 120
145 Number of cached large vnodes (-l) 200 400 600
146 Number of cached small vnodes (-s) 200 400 600
147 Maximum volume cache size (-vc) 200 400 600
148 Number of callbacks (-cb) 20,000 60,000 64,000
149 Number of Rx packets (-rxpck) 100 150 200
151 To override any of the values, provide the indicated argument (which can
152 be combined with the B<-S> or B<-L> flag).
154 The amount of memory required for the File Server varies. The approximate
155 default memory usage is 751 KB when the B<-S> flag is used (small
156 configuration), 1.1 MB when all defaults are used (medium configuration),
157 and 1.4 MB when the B<-L> flag is used (large configuration). If
158 additional memory is available, increasing the value of the B<-cb> and
159 B<-vc> arguments can improve File Server performance most directly.
161 By default, the File Server allows a volume to exceed its quota by 1 MB
162 when an application is writing data to an existing file in a volume that
163 is full. The File Server still does not allow users to create new files in
164 a full volume. To change the default, use one of the following arguments:
170 Set the B<-spare> argument to the number of extra kilobytes that the File
171 Server allows as overage. A value of C<0> allows no overage.
175 Set the B<-pctspare> argument to the percentage of the volume's quota the
176 File Server allows as overage.
180 By default, the File Server implicitly grants the C<a> (administer) and
181 C<l> (lookup) permissions to system:administrators on the access control
182 list (ACL) of every directory in the volumes stored on its file server
183 machine. In other words, the group's members can exercise those two
184 permissions even when an entry for the group does not appear on an ACL. To
185 change the set of default permissions, use the B<-implicit> argument.
187 The File Server maintains a I<host current protection subgroup> (I<host
188 CPS>) for each client machine from which it has received a data access
189 request. Like the CPS for a user, a host CPS lists all of the Protection
190 Database groups to which the machine belongs, and the File Server compares
191 the host CPS to a directory's ACL to determine in what manner users on the
192 machine are authorized to access the directory's contents. When the B<pts
193 adduser> or B<pts removeuser> command is used to change the groups to
194 which a machine belongs, the File Server must recompute the machine's host
195 CPS in order to notice the change. By default, the File Server contacts
196 the Protection Server every two hours to recompute host CPSs, implying
197 that it can take that long for changed group memberships to become
198 effective. To change this frequency, use the B<-hr> argument.
200 The File Server stores volumes in partitions. A partition is a
201 filesystem or directory on the server machine that is named C</vicepX>
202 or C</vicepXX> where XX is "a" through "z" or "aa" though "iv". Up to
203 255 partitions are allowed. The File Server expects that the /vicepXX
204 directories are each on a dedicated filesystem. The File Server will
205 only use a /vicepXX if it's a mountpoint for another filesystem,
206 unless the file C</vicepXX/AlwaysAttach> exists. The data in the
207 partition is a special format that can only be access using OpenAFS
208 commands or an OpenAFS client.
210 The File Server generates the following message when a partition is nearly
213 No space left on device
215 This command does not use the syntax conventions of the AFS command
216 suites. Provide the command name and all option names in full.
220 Do not use the B<-k> and B<-w> arguments, which are intended for use
221 by the OpenAFS developers only. Changing them from their default
222 values can result in unpredictable File Server behavior. In any case,
223 on many operating systems the File Server uses native threads rather
224 than the LWP threads, so using the B<-k> argument to set the number of
225 LWP threads has no effect.
227 Do not specify both the B<-spare> and B<-pctspare> arguments. Doing so
228 causes the File Server to exit, leaving an error message in the
229 F</usr/afs/logs/FileLog> file.
231 Options that are available only on some system types, such as the B<-m>
232 and B<-lock> options, appear in the output generated by the B<-help>
233 option only on the relevant system type.
235 Currently, the maximum size of a volume is 2 terabytes (2^31 bytes)
236 and the maximum size of a /vicepX partition on a fileserver is 2^64
237 kilobytes. The maximum partition size in releases 1.4.7 and earlier is
238 2 terabytes (2^31 bytes). The maximum partition size for 1.5.x
239 releases 1.5.34 and earlier is 2 terabytes as well.
241 The maximum number of directory entries is 64,000 if all of the entries
242 have names that are 15 octets or less in length. A name that is 15 octets
243 long requires the use of only one block in the directory. Additional
244 sequential blocks are required to store entries with names that are longer
245 than 15 octets. Each additional block provides an additional length of 32
246 octets for the name of the entry. Note that if file names use an encoding
247 like UTF-8, a single character may be encoded into multiple octets.
249 In real world use, the maximum number of objects in an AFS directory
250 is usually between 16,000 and 25,000, depending on the average name
257 =item B<-auditlog> <I<log path>>
259 Set and enable auditing.
261 =item B<-audit-interface> (file | sysvmq)
263 Specifies what audit interface to use. The C<file> interface writes audit
264 messages to the file passed to B<-auditlog>. The C<sysvmq> interface
265 writes audit messages to a SYSV message (see L<msgget(2)> and
266 L<msgrcv(2)>). The message queue the C<sysvmq> interface writes to has the
267 key C<ftok(path, 1)>, where C<path> is the path specified in the
272 =item B<-d> <I<debug level>>
274 Sets the detail level for the debugging trace written to the
275 F</usr/afs/logs/FileLog> file. Provide one of the following values, each
276 of which produces an increasingly detailed trace: C<0>, C<1>, C<5>, C<25>,
277 and C<125>. The default value of C<0> produces only a few messages.
279 =item B<-p> <I<number of processes>>
281 Sets the number of threads (or LWPs) to run. Provide a positive integer.
282 The File Server creates and uses five threads for special purposes,
283 in addition to the number specified (but if this argument specifies
284 the maximum possible number, the File Server automatically uses five
285 of the threads for its own purposes).
287 The maximum number of threads can differ in each release of OpenAFS.
288 Consult the I<OpenAFS Release Notes> for the current release.
290 =item B<-spare> <I<number of spare blocks>>
292 Specifies the number of additional kilobytes an application can store in a
293 volume after the quota is exceeded. Provide a positive integer; a value of
294 C<0> prevents the volume from ever exceeding its quota. Do not combine
295 this argument with the B<-pctspare> argument.
297 =item B<-pctspare> <I<percentage spare>>
299 Specifies the amount by which the File Server allows a volume to exceed
300 its quota, as a percentage of the quota. Provide an integer between C<0>
301 and C<99>. A value of C<0> prevents the volume from ever exceeding its
302 quota. Do not combine this argument with the B<-spare> argument.
304 =item B<-b> <I<buffers>>
306 Sets the number of directory buffers. Provide a positive integer.
308 =item B<-l> <I<large vnodes>>
310 Sets the number of large vnodes available in memory for caching directory
311 elements. Provide a positive integer.
313 =item B<-s> <I<small nodes>>
315 Sets the number of small vnodes available in memory for caching file
316 elements. Provide a positive integer.
318 =item B<-vc> <I<volume cachesize>>
320 Sets the number of volumes the File Server can cache in memory. Provide a
323 =item B<-w> <I<call back wait interval>>
325 Sets the interval at which the daemon spawned by the File Server performs
326 its maintenance tasks. Do not use this argument; changing the default
327 value can cause unpredictable behavior.
329 =item B<-cb> <I<number of callbacks>>
331 Sets the number of callbacks the File Server can track. Provide a positive
336 Prints the following banner to F</dev/console> about every 10 minutes.
338 File Server is running at I<time>.
342 Prevents the File Server from breaking the callbacks that Cache Managers
343 hold on a volume that the File Server is reattaching after the volume was
344 offline (as a result of the B<vos restore> command, for example). Use of
345 this flag is strongly discouraged.
347 =item B<-implicit> <I<admin mode bits>>
349 Defines the set of permissions granted by default to the
350 system:administrators group on the ACL of every directory in a volume
351 stored on the file server machine. Provide one or more of the standard
352 permission letters (C<rlidwka>) and auxiliary permission letters
353 (C<ABCDEFGH>), or one of the shorthand notations for groups of permissions
354 (C<all>, C<none>, C<read>, and C<write>). To review the meaning of the
355 permissions, see the B<fs setacl> reference page.
359 Don't allow writes to this fileserver.
361 =item B<-hr> <I<number of hours between refreshing the host cps>>
363 Specifies how often the File Server refreshes its knowledge of the
364 machines that belong to protection groups (refreshes the host CPSs for
365 machines). The File Server must update this information to enable users
366 from machines recently added to protection groups to access data for which
367 those machines now have the necessary ACL permissions.
369 =item B<-busyat> <I<< redirect clients when queue > n >>>
371 Defines the number of incoming RPCs that can be waiting for a response
372 from the File Server before the File Server returns the error code
373 C<VBUSY> to the Cache Manager that sent the latest RPC. In response, the
374 Cache Manager retransmits the RPC after a delay. This argument prevents
375 the accumulation of so many waiting RPCs that the File Server can never
376 process them all. Provide a positive integer. The default value is
379 =item B<-rxpck> <I<number of rx extra packets>>
381 Controls the number of Rx packets the File Server uses to store data for
382 incoming RPCs that it is currently handling, that are waiting for a
383 response, and for replies that are not yet complete. Provide a positive
388 Writes a trace of the File Server's operations on Rx packets to the file
389 F</usr/afs/logs/rx_dbg>.
393 Writes a trace of the File Server's operations on Rx events (such as
394 retransmissions) to the file F</usr/afs/logs/rx_dbg>.
396 =item B<-rxmaxmtu> <I<bytes>>
398 Defines the maximum size of an MTU. The value must be between the
399 minimum and maximum packet data sizes for Rx.
403 Allows the server to send and receive jumbograms. A jumbogram is
404 a large-size packet composed of 2 to 4 normal Rx data packets that share
405 the same header. The fileserver does not use jumbograms by default, as some
406 routers are not capable of properly breaking the jumbogram into smaller
407 packets and reassembling them.
411 Deprecated; jumbograms are disabled by default.
415 Force the fileserver to only bind to one IP address.
417 =item B<-allow-dotted-principals>
419 By default, the RXKAD security layer will disallow access by Kerberos
420 principals with a dot in the first component of their name. This is to avoid
421 the confusion where principals user/admin and user.admin are both mapped to the
422 user.admin PTS entry. Sites whose Kerberos realms don't have these collisions
423 between principal names may disable this check by starting the server
428 Sets values for many arguments in a manner suitable for a large file
429 server machine. Combine this flag with any option except the B<-S> flag;
430 omit both flags to set values suitable for a medium-sized file server
435 Sets values for many arguments in a manner suitable for a small file
436 server machine. Combine this flag with any option except the B<-L> flag;
437 omit both flags to set values suitable for a medium-sized file server
440 =item B<-k> <I<stack size>>
442 Sets the LWP stack size in units of 1 kilobyte. Do not use this argument,
443 and in particular do not specify a value less than the default of C<24>.
445 =item B<-realm> <I<Kerberos realm name>>
447 Defines the Kerberos realm name for the File Server to use. If this
448 argument is not provided, it uses the realm name corresponding to the cell
449 listed in the local F</usr/afs/etc/ThisCell> file.
451 =item B<-udpsize> <I<size of socket buffer in bytes>>
453 Sets the size of the UDP buffer, which is 64 KB by default. Provide a
454 positive integer, preferably larger than the default.
456 =item B<-sendsize> <I<size of send buffer in bytes>>
458 Sets the size of the send buffer, which is 16384 bytes by default.
460 =item B<-abortthreshold> <I<abort threshold>>
462 Sets the abort threshold, which is triggered when an AFS client sends
463 a number of FetchStatus requests in a row and all of them fail due to
464 access control or some other error. When the abort threshold is
465 reached, the file server starts to slow down the responses to the
466 problem client in order to reduce the load on the file server.
468 The throttling behaviour can cause issues especially for some versions
469 of the Windows OpenAFS client. When using Windows Explorer to navigate
470 the AFS directory tree, directories with only "look" access for the
471 current user may load more slowly because of the throttling. This is
472 because the Windows OpenAFS client sends FetchStatus calls one at a
473 time instead of in bulk like the Unix Open AFS client.
475 Setting the threshold to 0 disables the throttling behavior. This
476 option is available in OpenAFS versions 1.4.1 and later.
478 =item B<-enable_peer_stats>
480 Activates the collection of Rx statistics and allocates memory for their
481 storage. For each connection with a specific UDP port on another machine,
482 a separate record is kept for each type of RPC (FetchFile, GetStatus, and
483 so on) sent or received. To display or otherwise access the records, use
484 the Rx Monitoring API.
486 =item B<-enable_process_stats>
488 Activates the collection of Rx statistics and allocates memory for their
489 storage. A separate record is kept for each type of RPC (FetchFile,
490 GetStatus, and so on) sent or received, aggregated over all connections to
491 other machines. To display or otherwise access the records, use the Rx
494 =item B<-syslog [<loglevel>]
496 Use syslog instead of the normal logging location for the fileserver
497 process. If provided, log messages are at <loglevel> instead of the
502 Use MR-AFS (Multi-Resident) style logging. This option is deprecated.
506 Offer the SANEACLS capability for the fileserver. This option is
507 currently unimplemented.
511 Prints the online help for this command. All other valid options are
514 =item B<-fs-state-dont-save>
516 When present, fileserver state will not be saved during shutdown. Default
519 This option is only supported by the demand-attach file server.
521 =item B<-fs-state-dont-restore>
523 When present, fileserver state will not be restored during startup.
524 Default is to restore state on startup.
526 This option is only supported by the demand-attach file server.
528 =item B<-fs-state-verify> (none | save | restore | both)
530 This argument controls the behavior of the state verification mechanism.
531 A value of C<none> turns off all verification. A value of C<save> only
532 performs the verification steps prior to saving state to disk. A value
533 of C<restore> only performs the verification steps after restoring state
534 from disk. A value of C<both> performs all verifications steps both
535 prior to save and following a restore.
537 The default is C<both>.
539 This option is only supported by the demand-attach file server.
541 =item B<-vhashsize <I<size>>
543 The log(2) number of of volume hash buckets. Default is 8 (i.e., by
544 default, there are 2^8 = 256 volume hash buckets).
546 This option is only supported by the demand-attach file server.
548 =item B<-vlruthresh <I<minutes>>
550 The number of minutes of inactivity before a volume is eligible for soft
551 detachment. Default is 120 minutes.
553 This option is only supported by the demand-attach file server.
555 =item B<-vlruinterval <I<seconds>>
557 The number of seconds between VLRU candidate queue scan. The default is
560 This option is only supported by the demand-attach file server.
562 =item B<-vlrumax <I<positive integer>>
564 The maximum number of volumes which can be soft detached in a single pass
565 of the scanner. Default is 8 volumes.
567 This option is only supported by the demand-attach file server.
569 =item B<-vattachpar> <I<number of volume attach threads>>
571 The number of threads assigned to attach and detach volumes. The default
572 is 1. Warning: many of the I/O parallism features of Demand-Attach
573 Fileserver are turned off when the number of volume attach threads is only
576 This option is only meaningful for a file server built with pthreads
579 =item B<-m> <I<min percentage spare in partition>>
581 Specifies the percentage of each AFS server partition that the AIX version
582 of the File Server creates as a reserve. Specify an integer value between
583 C<0> and C<30>; the default is 8%. A value of C<0> means that the
584 partition can become completely full, which can have serious negative
585 consequences. This option is not supported on platforms other than AIX.
589 Prevents any portion of the fileserver binary from being paged (swapped)
590 out of memory on a file server machine running the IRIX operating system.
591 This option is not supported on platforms other than IRIX.
597 The following B<bos create> command creates an fs process on the file
598 server machine C<fs2.abc.com> that uses the large configuration size, and
599 allows volumes to exceed their quota by 10%. Type the command on a single
602 % bos create -server fs2.abc.com -instance fs -type fs \
603 -cmd "/usr/afs/bin/fileserver -pctspare 10 \
604 -L" /usr/afs/bin/volserver /usr/afs/bin/salvager
607 =head1 TROUBLESHOOTING
609 Sending process signals to the File Server Process can change its
610 behavior in the following ways:
612 Process Signal OS Result
613 ---------------------------------------------------------------------
615 File Server XCPU Unix Prints a list of client IP
618 File Server USR2 Windows Prints a list of client IP
621 File Server POLL HPUX Prints a list of client IP
624 Any server TSTP Any Increases Debug level by a power
625 of 5 -- 1,5,25,125, etc.
626 This has the same effect as the
627 -d XXX command-line option.
629 Any Server HUP Any Resets Debug level to 0
631 File Server TERM Any Run minor instrumentation over
632 the list of descriptors.
634 Other Servers TERM Any Causes the process to quit.
636 File Server QUIT Any Causes the File Server to Quit.
637 Bos Server knows this.
639 The basic metric of whether an AFS file server is doing well is the number
640 of connections waiting for a thread,
641 which can be found by running the following command:
643 % rxdebug <server> | grep waiting_for | wc -l
645 Each line returned by C<rxdebug> that contains the text "waiting_for"
646 represents a connection that's waiting for a file server thread.
648 If the blocked connection count is ever above 0, the server is having
649 problems replying to clients in a timely fashion. If it gets above 10,
650 roughly, there will be noticable slowness by the user. The total number of
651 connections is a mostly irrelevant number that goes essentially
652 monotonically for as long as the server has been running and then goes back
653 down to zero when it's restarted.
655 The most common cause of blocked connections rising on a server is some
656 process somewhere performing an abnormal number of accesses to that server
657 and its volumes. If multiple servers have a blocked connection count, the
658 most likely explanation is that there is a volume replicated between those
659 servers that is absorbing an abnormally high access rate.
661 To get an access count on all the volumes on a server, run:
663 % vos listvol <server> -long
665 and save the output in a file. The results will look like a bunch of B<vos
666 examine> output for each volume on the server. Look for lines like:
668 40065 accesses in the past day (i.e., vnode references)
670 and look for volumes with an abnormally high number of accesses. Anything
671 over 10,000 is fairly high, but some volumes like root.cell and other
672 volumes close to the root of the cell will have that many hits routinely.
673 Anything over 100,000 is generally abnormally high. The count resets about
676 Another approach that can be used to narrow the possibilities for a
677 replicated volume, when multiple servers are having trouble, is to find all
678 replicated volumes for that server. Run:
680 % vos listvldb -server <server>
682 where <server> is one of the servers having problems to refresh the VLDB
685 % vos listvldb -server <server> -part <partition>
687 to get a list of all volumes on that server and partition, including every
688 other server with replicas.
690 Once the volume causing the problem has been identified, the best way to
691 deal with the problem is to move that volume to another server with a low
692 load or to stop any runaway programs that are accessing that volume
693 unnecessarily. Often the volume will be enough information to tell what's
696 If you still need additional information about who's hitting that server,
697 sometimes you can guess at that information from the failed callbacks in the
698 F<FileLog> log in F</var/log/afs> on the server, or from the output of:
700 % /usr/afsws/etc/rxdebug <server> -rxstats
702 but the best way is to turn on debugging output from the file server.
703 (Warning: This generates a lot of output into FileLog on the AFS server.)
704 To do this, log on to the AFS server, find the PID of the fileserver
709 where <pid> is the PID of the file server process. This will raise the
710 debugging level so that you'll start seeing what people are actually doing
711 on the server. You can do this up to three more times to get even more
712 output if needed. To reset the debugging level back to normal, use (The
713 following command will NOT terminate the file server):
717 The debugging setting on the File Server should be reset back to normal when
718 debugging is no longer needed. Otherwise, the AFS server may well fill its
719 disks with debugging output.
721 The lines of the debugging output that are most useful for debugging load
724 SAFS_FetchStatus, Fid = 2003828163.77154.82248, Host 171.64.15.76
725 SRXAFS_FetchData, Fid = 2003828163.77154.82248
727 (The example above is partly truncated to highlight the interesting
728 information). The Fid identifies the volume and inode within the volume;
729 the volume is the first long number. So, for example, this was:
731 % vos examine 2003828163
732 pubsw.matlab61 2003828163 RW 1040060 K On-line
733 afssvr5.Stanford.EDU /vicepa
734 RWrite 2003828163 ROnly 2003828164 Backup 2003828165
736 Creation Mon Aug 6 16:40:55 2001
737 Last Update Tue Jul 30 19:00:25 2002
738 86181 accesses in the past day (i.e., vnode references)
740 RWrite: 2003828163 ROnly: 2003828164 Backup: 2003828165
742 server afssvr5.Stanford.EDU partition /vicepa RW Site
743 server afssvr11.Stanford.EDU partition /vicepd RO Site
744 server afssvr5.Stanford.EDU partition /vicepa RO Site
746 and from the Host information one can tell what system is accessing that
749 Note that the output of L<vos_examine(1)> also includes the access count, so
750 once the problem has been identified, vos examine can be used to see if the
751 access count is still increasing. Also remember that you can run vos
752 examine on the read-only replica (e.g., pubsw.matlab61.readonly) to see the
753 access counts on the read-only replica on all of the servers that it's
756 =head1 PRIVILEGE REQUIRED
758 The issuer must be logged in as the superuser C<root> on a file server
759 machine to issue the command at a command shell prompt. It is conventional
760 instead to create and start the process by issuing the B<bos create>
776 IBM Corporation 2000. <http://www.ibm.com/> All Rights Reserved.
778 This documentation is covered by the IBM Public License Version 1.0. It was
779 converted from HTML to POD by software written by Chas Williams and Russ
780 Allbery, based on work by Alf Wachsmann and Elizabeth Cassell.