one thing that i haven't seen in all this mail...are you running the
client commands on one of the afs servers? in other words, do your
servers have afs clients installed on them?
when you do certain things that could cause the client to hang, you
don't want the client that's hanging be the one that's doing the operation.
so...just to be clear, are you running your 'vos' commands on an actual
client machine, or on one of your afs server machines?
anne
Andreas Hirczy wrote:
"Derrick Brashear" <[EMAIL PROTECTED]> writes:
==> /var/log/openafs/VolserLog <==
FSYNC_clientInit failed (giving up!): Connection refused
Wed Jul 23 21:26:08 2008
: Assertion failed! file ../vol/volume.c, line 705.
dead volserver would of course explain a hang. the volserver will restart
with an fs outage.
But these were the only messages indicating a serious failure today.
Lars Schimmer meant a "vos syncvldb" could help, but "vos syncvldb faepsv05 a
-dryrun -localauth -verbose" seems to hang also. Maybe he is right and i have
to remove the VLDB first? I really do not like this method very much.
Thank god it's late here in europe, so there are no users breathing into my
neck.
got a corefile?
Sorry no - I'll readjust the limits - now the salvager ran again :)
Whats strange, there are ~600 user volumes on the disk, but only RO replicas
appear to have been checked in the salvager log.
Andreas
_______________________________________________
OpenAFS-info mailing list
[email protected]
https://lists.openafs.org/mailman/listinfo/openafs-info
