Index: openafs/doc/man-pages/README diff -c openafs/doc/man-pages/README:1.8.2.16 openafs/doc/man-pages/README:1.8.2.17 *** openafs/doc/man-pages/README:1.8.2.16 Tue Dec 25 17:26:43 2007 --- openafs/doc/man-pages/README Tue Feb 19 10:28:55 2008 *************** *** 204,210 **** copyauth fs cscpolicy fs memdump - fs minidump fs monitor fs rxstatpeer fs rxstatproc --- 204,209 ---- Index: openafs/doc/man-pages/pod1/fs_listquota.pod diff -c openafs/doc/man-pages/pod1/fs_listquota.pod:1.5.2.1 openafs/doc/man-pages/pod1/fs_listquota.pod:1.5.2.2 *** openafs/doc/man-pages/pod1/fs_listquota.pod:1.5.2.1 Sun Nov 11 18:51:05 2007 --- openafs/doc/man-pages/pod1/fs_listquota.pod Tue Feb 19 10:28:56 2008 *************** *** 28,33 **** --- 28,44 ---- To set volume quota, use the B or B command. + =head1 CAUTIONS + + Currently, the maximum size of a volume is 2 terabytes (2^31 bytes) + and the maximum size of a /vicepX partition on a fileserver is also 2 + terabytes. The fileserver will not report an error when it has access + to a partition larger than 2 terabytes, but it will probably fail if + the administrator attempts to use more than 2 terabytes of space. In + addition, there are reports of erroneous disk usage numbers when + B or other OpenAFS disk reporting tools are used with + partitions larger than 2 terabytes. + =head1 OPTIONS =over 4 Index: openafs/doc/man-pages/pod1/fs_minidump.pod diff -c /dev/null openafs/doc/man-pages/pod1/fs_minidump.pod:1.1.2.2 *** /dev/null Tue Feb 19 22:42:26 2008 --- openafs/doc/man-pages/pod1/fs_minidump.pod Tue Feb 19 10:28:56 2008 *************** *** 0 **** --- 1,47 ---- + =head1 NAME + + fs_minidump - Generate a minidump from the current afsd service + + =head1 SYNOPSIS + + =for html +
+ + B [B<-help>] + + =for html +
+ + =head1 DESCRIPTION + + B generates a mini dump file containing the current stack + of the afsd_service.exe process. This output can be very helpful when + debugging the AFS Client Service when it is unresponsive to SMB/CIFS + requests. + + =head1 CAUTIONS + + This command is only available in OpenAFS for Windows version 1.4 and later. + + =head1 OPTIONS + + =over 4 + + =item B<-help> + + Prints the online help for this command. All other valid options are + ignored. + + =back + + =head1 SEE ALSO + + L + + =head1 COPYRIGHT + + Copyright 2007 Jason Edgecombe + + This documentation is covered by the BSD License as written in the + doc/LICENSE file. This man page was written by Jason Edgecombe for + OpenAFS. Index: openafs/doc/man-pages/pod1/fs_quota.pod diff -c openafs/doc/man-pages/pod1/fs_quota.pod:1.3.2.1 openafs/doc/man-pages/pod1/fs_quota.pod:1.3.2.2 *** openafs/doc/man-pages/pod1/fs_quota.pod:1.3.2.1 Sun Nov 11 18:51:05 2007 --- openafs/doc/man-pages/pod1/fs_quota.pod Tue Feb 19 10:28:56 2008 *************** *** 24,29 **** --- 24,40 ---- To set volume quota, use the B or B command. + =head1 CAUTIONS + + Currently, the maximum size of a volume is 2 terabytes (2^31 bytes) + and the maximum size of a /vicepX partition on a fileserver is also 2 + terabytes. The fileserver will not report an error when it has access + to a partition larger than 2 terabytes, but it will probably fail if + the administrator attempts to use more than 2 terabytes of space. In + addition, there are reports of erroneous disk usage numbers when + B or other OpenAFS disk reporting tools are used with + partitions larger than 2 terabytes. + =head1 OPTIONS =over 4 Index: openafs/doc/man-pages/pod1/fs_setquota.pod diff -c openafs/doc/man-pages/pod1/fs_setquota.pod:1.4.2.1 openafs/doc/man-pages/pod1/fs_setquota.pod:1.4.2.2 *** openafs/doc/man-pages/pod1/fs_setquota.pod:1.4.2.1 Sun Nov 11 18:51:05 2007 --- openafs/doc/man-pages/pod1/fs_setquota.pod Tue Feb 19 10:28:56 2008 *************** *** 29,34 **** --- 29,45 ---- To display a volume's quota, use the B, B, or B command. + =head1 CAUTIONS + + Currently, the maximum size of a volume is 2 terabytes (2^31 bytes) + and the maximum size of a /vicepX partition on a fileserver is also 2 + terabytes. The fileserver will not report an error when it has access + to a partition larger than 2 terabytes, but it will probably fail if + the administrator attempts to use more than 2 terabytes of space. In + addition, there are reports of erroneous disk usage numbers when + B or other OpenAFS disk reporting tools are used with + partitions larger than 2 terabytes. + =head1 OPTIONS =over 4 Index: openafs/doc/man-pages/pod1/fs_setvol.pod diff -c openafs/doc/man-pages/pod1/fs_setvol.pod:1.4.2.1 openafs/doc/man-pages/pod1/fs_setvol.pod:1.4.2.2 *** openafs/doc/man-pages/pod1/fs_setvol.pod:1.4.2.1 Sun Nov 11 18:51:05 2007 --- openafs/doc/man-pages/pod1/fs_setvol.pod Tue Feb 19 10:28:56 2008 *************** *** 36,41 **** --- 36,52 ---- To set quota on one volume at a time, use the B command. + =head1 CAUTIONS + + Currently, the maximum size of a volume is 2 terabytes (2^31 bytes) + and the maximum size of a /vicepX partition on a fileserver is also 2 + terabytes. The fileserver will not report an error when it has access + to a partition larger than 2 terabytes, but it will probably fail if + the administrator attempts to use more than 2 terabytes of space. In + addition, there are reports of erroneous disk usage numbers when + B or other OpenAFS disk reporting tools are used with + partitions larger than 2 terabytes. + =head1 OPTIONS =over 4 Index: openafs/doc/man-pages/pod1/vos_addsite.pod diff -c openafs/doc/man-pages/pod1/vos_addsite.pod:1.4.2.1 openafs/doc/man-pages/pod1/vos_addsite.pod:1.4.2.2 *** openafs/doc/man-pages/pod1/vos_addsite.pod:1.4.2.1 Sun Nov 11 18:51:05 2007 --- openafs/doc/man-pages/pod1/vos_addsite.pod Tue Feb 19 10:28:56 2008 *************** *** 9,21 **** B S<<< B<-server> > >>> S<<< B<-partition> > >>> ! S<<< B<-id> > >>> S<<< [B<-cell> >] >>> ! [B<-noauth>] [B<-localauth>] [B<-verbose>] [B<-help>] B S<<< B<-s> > >>> S<<< B<-p> > >>> ! S<<< B<-i> > >>> S<<< [B<-c> >] >>> ! [B<-n>] [B<-l>] [B<-v>] [B<-h>] =for html --- 9,22 ---- B S<<< B<-server> > >>> S<<< B<-partition> > >>> ! S<<< B<-id> > >>> S<<< B<-valid> > >>> ! S<<< [B<-cell> >] >>> [B<-noauth>] [B<-localauth>] ! [B<-verbose>] [B<-help>] B S<<< B<-s> > >>> S<<< B<-p> > >>> ! S<<< B<-i> > >>> S<<< B<-valid> > >>> ! S<<< [B<-c> >] >>> [B<-n>] [B<-l>] [B<-v>] [B<-h>] =for html *************** *** 68,74 **** Specifies either the complete name or volume ID number of the read/write source volume. ! =item B<-cell> > Names the cell in which to run the command. Do not combine this argument with the B<-localauth> flag. For more details, see L. --- 69,84 ---- Specifies either the complete name or volume ID number of the read/write source volume. ! =item B<-valid> > ! ! Specifies the volume ID number of the existing release-equivalent ! volume that is not already marked as a replica. This is useful when an ! existing read-only volume is dumped and restored with the B<-readonly> ! flag at the new site. This option is available in OpenAFS clients ! 1.4.7 or later and 1.5.31 and later. This option can be used with ! OpenAFS server versions later than 1.4.1 or 1.5.0. ! ! =Item B<-cell> > Names the cell in which to run the command. Do not combine this argument with the B<-localauth> flag. For more details, see L. Index: openafs/doc/man-pages/pod1/vos_examine.pod diff -c openafs/doc/man-pages/pod1/vos_examine.pod:1.4.2.1 openafs/doc/man-pages/pod1/vos_examine.pod:1.4.2.2 *** openafs/doc/man-pages/pod1/vos_examine.pod:1.4.2.1 Sun Nov 11 18:51:05 2007 --- openafs/doc/man-pages/pod1/vos_examine.pod Tue Feb 19 10:28:57 2008 *************** *** 32,37 **** --- 32,48 ---- To display the volume header only, use the B command. To display information from the VLDB only, use the B command. + =head1 CAUTIONS + + Currently, the maximum size of a volume is 2 terabytes (2^31 bytes) + and the maximum size of a /vicepX partition on a fileserver is also 2 + terabytes. The fileserver will not report an error when it has access + to a partition larger than 2 terabytes, but it will probably fail if + the administrator attempts to use more than 2 terabytes of space. In + addition, there are reports of erroneous disk usage numbers when + B or other OpenAFS disk reporting tools are used with + partitions larger than 2 terabytes. + =head1 OPTIONS =over 4 Index: openafs/doc/man-pages/pod1/vos_partinfo.pod diff -c openafs/doc/man-pages/pod1/vos_partinfo.pod:1.3.2.1 openafs/doc/man-pages/pod1/vos_partinfo.pod:1.3.2.2 *** openafs/doc/man-pages/pod1/vos_partinfo.pod:1.3.2.1 Sun Nov 11 18:51:05 2007 --- openafs/doc/man-pages/pod1/vos_partinfo.pod Tue Feb 19 10:28:57 2008 *************** *** 25,30 **** --- 25,41 ---- that file server machine. The Volume Location Database (VLDB) is not consulted. + =head1 CAUTIONS + + Currently, the maximum size of a volume is 2 terabytes (2^31 bytes) + and the maximum size of a /vicepX partition on a fileserver is also 2 + terabytes. The fileserver will not report an error when it has access + to a partition larger than 2 terabytes, but it will probably fail if + the administrator attempts to use more than 2 terabytes of space. In + addition, there are reports of erroneous disk usage numbers when + B or other OpenAFS disk reporting tools are used with + partitions larger than 2 terabytes. + =head1 OPTIONS =over 4 Index: openafs/doc/man-pages/pod8/afsd.pod diff -c openafs/doc/man-pages/pod8/afsd.pod:1.6.2.4 openafs/doc/man-pages/pod8/afsd.pod:1.6.2.5 *** openafs/doc/man-pages/pod8/afsd.pod:1.6.2.4 Sun Aug 5 19:19:33 2007 --- openafs/doc/man-pages/pod8/afsd.pod Tue Feb 19 10:28:57 2008 *************** *** 627,633 **** =item B<-rxpck> > ! Set rx_extraPackets to this value. =item B<-settime> --- 627,637 ---- =item B<-rxpck> > ! Set rx_extraPackets to this value. This sets the number of extra Rx ! packet structures that are available to handle Rx connections. This ! value should be increased if the "rxdebug 127.0.0.1 -port 7001 ! -rxstats" command shows no free Rx packets. Increasing this value may ! improve OpenAFS client performance in some circumstances. =item B<-settime> Index: openafs/doc/txt/winnotes/afs-changes-since-1.2.txt diff -c openafs/doc/txt/winnotes/afs-changes-since-1.2.txt:1.72.2.44 openafs/doc/txt/winnotes/afs-changes-since-1.2.txt:1.72.2.46 *** openafs/doc/txt/winnotes/afs-changes-since-1.2.txt:1.72.2.44 Sat Feb 9 07:39:21 2008 --- openafs/doc/txt/winnotes/afs-changes-since-1.2.txt Mon Feb 18 23:19:09 2008 *************** *** 1,3 **** --- 1,73 ---- + Since 1.5.31 + * Do not attempt to search for a cell name that matches one + of the special share names "svrsvc", "wkssvc", "ipc$" + + * Issue permission denied warnings from afscreds if attempts + to modify the startup shortcut or registry values fail. + This happens under Vista UAC. + + * Do not return BAD_NETWORK_ERROR in response to attempts + to create directories or files in the Freelance root.afs + volume. Instead return ACCESS_DENIED. + + BAD_NETWORK_ERROR was being sent because the Freelance cell + has no vldb servers. Short circuit the error by testing for + freelance in CreateFile and MakeDir + + * Treat srvsvc, wkssvc and ipc$ as pseudo files. Permit them + to be opened and closed without actually existing. For now + we treat them as equivalent to ioctls but this should + eventually change. + + * Fix RAP processing to not reject names that exist in the + root.afs volume for GetInfo queries. + + * In afscreds, use GetUserNameEx to obtain the username instead + of searching the registry. Try UserPrincipalName first and + fallback to SamCompatible. + + * Stop linking to rpcns4.dll which is no longer supported on + Vista and 2008. TaAfsAdmSvr is going to have to be + redesigned. + + * When processing dfs referral requests, if the sharename is + a partial match and therefore will not be added automatically + to the share list, make sure that we return an error. + + * Avoid a crash when logging VNOVOL errors returned from + cm_CheckOfflineVolume. + + * When trace logging is disabled, do not permit osi_LogSaveString + to perform the string copying. By disabling the string + copies, throughput of the service more than doubles. + + * when checking offline volumes, update the cell vlserver info + if required and don't perform a check if there are no servers + in the list. + + * Add volumes in the vl_unknown state to the list of objects to be + checked as offline or retried when an allbusy error is received + in cm_Analyze. + + * Add support for configuring rx_ExtraPackets + + * All calls to buf_Get() must be protected by a read lock on the + cm_scache_t bufCreateLock + + * When a MergeStatus results in the invalidation of buffers, do + not remove buffers from the hash tables that have active references. + + * Upon receiving a VNOVNODE error from a file server, be sure to + invalidate any file locks. This prevents on-going attempts to + extend the locks and will cause subsequent attempts to access + the file to receive a invalid handle error. + + * Prevent smb_ReceiveTran2SearchDir from adding terminating NULs + to directory entry names. + + * No longer discard tokens when RXKADBADTICKET error is received. + Instead return STATUS_NO_KERB_KEY error. + Since 1.5.30 * Add "cmdebug -cellservdb" option and client service implementation permits querying the vldb server for each