Hi everyone, Thanks to Jeff Altman for helping me with a server issue a week ago. Thanks to Derrick for helping me on the jabber chat on sunday to salvage a corrupt RO volume by RW id.
I have a similar problem, but this time, the volume won't salvage by RO id or RW id: Here is the FileLog: Tue Aug 11 08:16:21 2009 VAttachVolume: Error reading diskDataHandle vol header /vicepb//V0537144103.vol; error=101 Tue Aug 11 08:16:21 2009 VAttachVolume: Error attaching volume /vicepb//V0537144103.vol; volume needs salvage; error=101 Tue Aug 11 08:16:29 2009 VAttachVolume: Error reading diskDataHandle vol header /vicepb//V0537144103.vol; error=101 Tue Aug 11 08:16:29 2009 VAttachVolume: Error attaching volume /vicepb//V0537144103.vol; volume needs salvage; error=101 Here is the salvage log using the RO id: fs# cat SalvageLog.old @(#) OpenAFS 1.4.10 built 2009-06-05 08/11/2009 08:12:57 STARTING AFS SALVAGER 2.4 (/usr/afs/bin/salvager /vicepb 537144103) 08/11/2009 08:13:07 Scanning inodes on device /dev/rdsk/c1t2d0s6... 08/11/2009 08:13:58 537144103 is a read-only volume; not salvaged Here is the salvage log for the RW id (presumably, RO ID-1): fs# cat SalvageLog @(#) OpenAFS 1.4.10 built 2009-06-05 08/11/2009 08:14:26 STARTING AFS SALVAGER 2.4 (/usr/afs/bin/salvager /vicepb 537144102) 08/11/2009 08:14:37 Scanning inodes on device /dev/rdsk/c1t2d0s6... 08/11/2009 08:15:28 No applicable vice inodes on c1t2d0s6; not salvaged 08/11/2009 08:15:28 0 nVolumesInInodeFile 0 Temporary file /vicepb/salvage.inodes.c1t2d0s6.1099 is missing... This volume isn't in VLDB so it I know it's unused. I found all of this out while upgrading my solaris 9 SPARC boxes form 1.4.6 to 1.4.10 with the background fssync patch. Any advice is appreciated. Thanks, Jason _______________________________________________ OpenAFS-info mailing list [email protected] https://lists.openafs.org/mailman/listinfo/openafs-info
