Appendix A. Frequently Asked Questions

The questions and answers listed in this appendix can help with troubleshooting BDSpro.

  1. Where is BDS server software stored?

    The BDS server is now located in /usr/etc instead of /usr/sbin. This is more consistent with other IRIX daemons.

  2. How do I change the configuration options passed to the server?

    The file /etc/config/BDSpro.config is passed to the BDS server as arguments. By default, it turns on logging and sends the results to /var/adm/bds.log.

  3. BDS is using a lot of memory. How can I limit it?

    Because BDS uses buffering to speed up file accesses, you may find that buffering takes up a lot of memory, particularly if you have many different applications accessing files. See “Specifying a Buffer Size”.

  4. Why am I not seeing big improvements in write performance?

    The improvements are a result of enabling write buffering. Write buffering is not enabled by default because it has the potential to lose data in the event of a server failure, and because, if a write error occurs, it is not reported until a subsequent I/O operation. See “Starting and Stopping the BDSpro Service” for more information.

  5. Why is mount locking up?

    As of BDSpro 2.0, you cannot mount a filesystem using BDS unless a BDS daemon running on the server. Just start up BDS on the server and the problem should be solved.

  6. I think my BDS server is dead or misbehaving. How do I restart it?

    A script in /etc/init.d starts and stops the BDS daemon. As root, type this command:

    # /etc/init.d/BDSpro start

    This stops all BDS daemons that were running and restarts them. Clients accessing BDS are automatically reconnected to the new BDS daemons.