[OpenAFS] fileserver goes down overnight
Anders Magnusson
ragge@ltu.se
Tue, 24 Mar 2009 19:02:29 +0100
david l goodrich wrote:
> On Tue, Mar 24, 2009 at 10:39:24AM -0700, Russ Allbery wrote:
>
>> david l goodrich <dlg@dsrw.org> writes:
>>
>>
>>> The past two nights, I've had one of my AFS fileserver go "down"
>>>
>>> I say "down" and not down because it's not totally nonfunctional.
>>>
>>> It thinks it's running fine:
>>>
>>> sprawl# bos status localhost -localauth
>>> Instance fs, currently running normally.
>>> Auxiliary status is: file server running.
>>>
>> bos status -long is generally more useful. However:
>>
> Can do:
> sprawl# bos status localhost -localauth -long
> Instance fs, (type is fs) currently running normally.
> Auxiliary status is: file server running.
> Process last started at Mon Mar 23 17:33:57 2009 (3 proc
> starts)
> Last exit at Mon Mar 23 17:33:57 2009
> Command 1 is '/usr/pkg/libexec/openafs/fileserver'
> Command 2 is '/usr/pkg/libexec/openafs/volserver'
> Command 3 is '/usr/pkg/libexec/openafs/salvager'
>
> sprawl# ps auxw | grep /openafs/
> root 376 0.0 0.0 2316 4 ? DW 5:33PM 0:00.83 /usr/pkg/libexec/openafs/volserver
> root 727 0.0 0.0 8664 2384 ? IW<a 5:33PM 0:18.29 /usr/pkg/libexec/openafs/fileserver
>
If the D flag in the ps line means the same on your system as on mine
you might
have problem. D usually stands for a process waiting for I/O, and if it
don't leave
that state it means that it never completes. The W flag normally stands
fro swapped out, and
you also seems to have nothing of the process resident.
You don't have any hardware complaints in messages?
-- Ragge