I use -fastrestart which is IIRC a compile-time option.

The liability is that some volumes may not be attached at startup.

The 'notifier' option in the BosConfig entry can be used to send email or to automatically salvage individual volumes.

Although I've had very good luck with this I will say that the notifier script is executed twice, not once, by the BosServer when specified for the fs entry -- apparently once for the fileserver and once for the volserver.  It's a nuisance.

All in all, however, almost every volume has been placed back into service immediately after every fileserver restart/crash.  Very few instances of off line or could not attach volumes.

For us that's a win -- instead of making all volumes on the server unavailable for upwards of 45 minutes, well over 90% of the users are never aware the fileserver went down at all, and with the notifier script automatic salvage (my script is still defective due to the 2x notifier script execution or I'd paste it here) I've had exactly one complaint from one user after multiple spontaneous crashes (not for a long time, thank you all developers!) and intentional file server kills.

YMMV.

Kim


Derrick Brashear wrote:


On Dec 19, 2007 9:50 AM, Jerry Normandin <[EMAIL PROTECTED]> wrote:

Sorry, left work just before I got your email. 

 

Yes I looked in the Boslog, this is what I found:

 

Tue Dec 18 11:04:38 2007: fs:file exited on signal 3


This is fine, kill -QUIT is the normal clean shutdown.
 

Tue Dec 18 11:05:41 2007: bos shutdown: volserver failed to shutdown within 60 s

econds

This was your issue, I have no idea why based on only that log message.


_______________________________________________ OpenAFS-info mailing list [email protected] https://lists.openafs.org/mailman/listinfo/openafs-info

Reply via email to