On Tue, 24 Jun 2008, Jeff Blaine wrote:

Okay, I'll bite:  Now what?

ADMIN% bos salvage fs1 c -volume 2023867266 -showlog
Starting salvage.
bos: waiting for salvage to complete.
bos: waiting for salvage to complete.
bos: waiting for salvage to complete.
bos: waiting for salvage to complete.
bos: waiting for salvage to complete.
bos: waiting for salvage to complete.
bos: waiting for salvage to complete.
bos: waiting for salvage to complete.
bos: waiting for salvage to complete.
bos: waiting for salvage to complete.
bos: waiting for salvage to complete.
bos: waiting for salvage to complete.
bos: waiting for salvage to complete.
bos: salvage completed
SalvageLog:
@(#) OpenAFS 1.4.6 built  2007-12-21
06/24/2008 17:26:54 STARTING AFS SALVAGER 2.4 (/usr/afs/bin/salvager
/vicepc 2023867266)
06/24/2008 17:27:04 Scanning inodes on device
/dev/rdsk/c3t6006016012341600D86B14C7E294DA11d0s3...
06/24/2008 17:28:03 2023867266 is a read-only volume; not salvaged

ADMIN% vos zap fs1 c 2023867266
Warning: Entry for volume number 2023867266 exists in VLDB (but we're
zapping it anyway!)
Could not start transaction on volume 2023867266
Volume needs to be salvaged
Error in vos zap command.
Volume needs to be salvaged

vos zap fs1 c 2023867266 -force

--
Eric Sturdivant
University of Maryland
Office of Information Technology
Distributed Computing Services
_______________________________________________
OpenAFS-info mailing list
OpenAFS-info@openafs.org
https://lists.openafs.org/mailman/listinfo/openafs-info

Reply via email to