I had a problem setting my cache size, so attempts to start openafs-client failed silently, giving no information to debug the problem, even when setting -verbose and -debug options. Looking at the initscript, I saw that stdout and stderror were always sent to /dev/null. I tweaked this to send the output to a file in /var/log/, and saw an easy-to-interpret message that my cache size was to big for my cache partition, and suggested a correct size to use. A minor tweak to /etc/openafs/cacheinfo and I was up and running. Reproducible: Always Steps to Reproduce: 1. Create a 2GB cache partition, format as ext2. (Mine came out slightly larger.) 2. Edit /etc/openafs/cacheinfo to designate a 2GB (2000000) cache size. 3. Run "/etc/init.d/openafs-client start" Actual Results: Client refuses to start Expected Results: Client should have started. As mentioned, based on the error message, I updated my cache size to 1960990, which is 95% of my rounded-up 2GB cache partition. Now it works. Rather than my tweaked initscript, I adopted a slightly cleaner fix. In "/etc/init.d/openafs-client" in the "choose_afsdoptions()" routine I added the lines : if [[ -z "$VERBOSE" ]]; then LOGSTART="/dev/null" LOGSTOP="/dev/null" else LOGSTART="/var/log/openafs/client.lastStart" LOGSTOP="/var/log/openafs/client.lastStop" fi Then in the "cleanstart()" and "stop()" procedures I replaced "/dev/null" with "${LOGSTART}" and "${LOGSTOP}" respectively. This way for normal operation, everything works as it does today, sending the chatter to /dev/null. But for debugging a problem you can define VERBOSE in "/etc/conf.d/openafs-client" and you'll get the needed and valuable output. Incidentally, the VERBOSE environment variable was already used in "/etc/init.d/openafs-client" even though it was not defined in "/etc/conf.d/openafs-client".
Fixed in 1.6.11.1
