It sounds like one of your rep sites for this volume is bad. Check the
VolserLog for any errors. To get it back fast, zap the RO sites and
re-release. It could also be the case that you have corruption in the
cache on this set of clients, but that is unlikely - this sounds a lot
more like a bad rep site.
[EMAIL PROTECTED] writes:
> One thing I noticed in the FileLog is that every time we vos release
> the volume we get the following message:
>
> Thu Feb 2 17:19:33 1995 VAttachVolume: Cannot read volume header
> /vicepb//V0536872893.vl
>
> Is this normal?
It can be. Occasionally volume operations fail to clean up after
themselves (ex: vos is killed midway through a move) and volumes are
left in an intermediate state. The fileserver will refuse to mount
these. Check the volume ID, see if it should be on this server. If you
get an unknown volume error, you have a dead clone volume on your
hands - don't worry about it. The next salvage will clear it up. If it
turns out it is a real volume, salvage. If it doesn't come back, you
have a problem (go to backups, etc.).
> Also in FileLog I see the following messages at various different times:
>
> Thu Feb 2 22:39:58 1995 CB: RCallBackConnectBack (host.c) failed for
> host a479153a.7001
Normal. A client became unresponsive on a callback check. Nothing to
worry about.
dan
cmu computing services
[EMAIL PROTECTED]
