Seconding what Dan said. Under 'normal' circumstances, you can get away with this. But if anything goes wrong with your afs server itself, you're in a deadly embrace -- since the server doesn't come up, the client fails and the sh*t hits the fan. Worse, if you've got server-side dependencies on having the afs client up (for example, other services run on the afs server depend on files in AFS), then it may be impossible to bring your file server up at all except by inserting a CD-ROM and hitting the power switch. And if your server doesn't happen to have a CD-ROM drive. . . so yeah, don't do that.
Steve On Jul 11, 2012, at 9:44 PM, Dan Hyde wrote: > There be dragons. We learned the had way a long time ago that it is possible > to have your server require you have a working client before the server would > start (before it had access to what the client could provide). Please > reconsider. > > On Jul 11, 2012, at 9:25 PM, "Lewis, Dave" <[email protected]> wrote: > >> Hi, >> >> On one of our fileservers, /afs is empty. (We're running the AFS client >> on the fileserver because I sometimes do client operations there.) All >> of our other servers and clients seem fine. >> >> I looked through the AFS log files and didn't see anything obvious (but >> I could have missed something). The /usr/vice/cache partition is ext3. >> >> CentOS 5.6, OpenAFS 1.4.14.1, 64-bit >> >> $ ls -la /afs >> total 8 >> drwxr-xr-x 2 root root 4096 Apr 14 2010 ./ >> drwxr-xr-x 34 root root 4096 May 26 19:16 ../ >> >> # service openafs-client status >> afsd (pid 4320) is running... >> >> # du -sh /usr/vice/cache >> 24M /usr/vice/cache >> >> # cat /usr/vice/etc/cacheinfo >> /afs:/usr/vice/cache:900000 >> >> $ cat /etc/sysconfig/openafs >> # OpenAFS Client Configuration >> AFSD_ARGS="-fakestat -stat 4000 -dcache 4000 -daemons 6 -volumes 256 >> -files 50000 -nosettime" >> >> # OpenAFS Server Configuration >> BOSSERVER_ARGS= >> >> >> On another server (set up the same way): >> >> $ ls -la /afs >> total 15 >> drwxrwxrwx 2 root root 2048 May 17 2000 ./ >> drwxr-xr-x 33 root root 4096 May 26 19:20 ../ >> lrwxr-xr-x 1 bin root 13 May 17 2000 cabi -> cabi.rfmh.org/ >> drwxrwxrwx 2 root root 2048 Jun 14 2011 .cabi.rfmh.org/ >> drwxrwxrwx 2 root root 2048 Jun 14 2011 cabi.rfmh.org/ >> >> # du -sh /usr/vice/cache >> 827M /usr/vice/cache >> >> Would it be safe to restart the AFS client and see if it fixes the >> problem? Since the computer is a server and I haven't figured out the >> cause of the problem, I thought I would ask here first. >> >> Thanks, >> Dave >> >> ============================================================== >> David P. Lewis >> Center for Advanced Brain Imaging, Division of Medical Physics >> The Nathan S. Kline Institute for Psychiatric Research >> 140 Old Orangeburg Road, Orangeburg, NY 10962 >> >> >> >> >> >> Conserve Resources. Print only when necessary. >> >> IMPORTANT NOTICE: This e-mail is meant only for the use of the intended >> recipient. It may contain confidential information which is legally >> privilegedor otherwise protected by law. If you received this e-mail in >> error or from someone who is not authorized to send it to you, you are >> strictly prohibited from reviewing, using, disseminating, distributing or >> copying the e-mail. PLEASE NOTIFY US IMMEDIATELY OF THE ERROR BY RETURN >> E-MAIL AND DELETE THIS MESSAGE FROM YOUR SYSTEM. Thank you for your >> cooperation. >> _______________________________________________ >> OpenAFS-info mailing list >> [email protected] >> https://lists.openafs.org/mailman/listinfo/openafs-info >> >> > _______________________________________________ > OpenAFS-info mailing list > [email protected] > https://lists.openafs.org/mailman/listinfo/openafs-info _______________________________________________ OpenAFS-info mailing list [email protected] https://lists.openafs.org/mailman/listinfo/openafs-info
