Daniel Debertin wrote: => 'vos examine' output:
afs0# vos examine root.afs -noauth **** Could not attach volume 536870912 ****RWrite: 536870912 number of sites -> 1 server afs0.msi.umn.edu partition /vicepa RW Site
This tells you that the volume exists in the volume location db and which server the volume is supposed to exist on.
So there's a volume there, but it can't be attached for some reason.
>
VolserLog is the only logfile that contains errors: Mon Aug 11 15:19:48 2008 Unable to connect to file server; will retry at need Mon Aug 11 15:19:48 2008 Starting AFS Volserver 2.0 (/usr/afs/bin/volserver) Mon Aug 11 15:19:56 2008 VCreateVolume: Problem writing to inode 38467488 (err=9)
And here is your problem. The inode cannot be written to because err=9, EBADF, which means invalid file descriptor.
Mon Aug 11 15:19:56 2008 1 Volser: CreateVolume: Unable to create the volume; aborted, error code 103 Mon Aug 11 15:19:56 2008 : Error 103
As a result of the above error, the volserver is returning 103, VNOVOL, to indicate that the volume does not exist.
Mon Aug 11 15:24:17 2008 VAttachVolume: Error reading volume header /vicepa/V0536870912.vol Mon Aug 11 15:24:17 2008 1 Volser: ListVolumes: Could not attach volume 536870912 (/vicepa:V0536870912.vol), error=101
and error 101, VSALVAGE, to indicate that the volume needs to be salvaged before it can be attached.
What does the salvage log say when you attempt to salvage this volume?
smime.p7s
Description: S/MIME Cryptographic Signature
