] > SalvageLog starts: ] > @(#) OpenAFS 1.4.6 built 2007-12-17 ] > 04/01/2008 17:15:21 STARTING AFS SALVAGER 2.4 (/usr/afs/bin/salvager -f) ] > 04/01/2008 17:15:21 Starting salvage of file system partition /vicepa ] > 04/01/2008 17:15:21 SALVAGING FILE SYSTEM PARTITION /vicepa (device=c1t1d0s6) ] > 04/01/2008 17:15:21 ***Forced salvage of all volumes on this partition*** ] > 04/01/2008 17:15:31 Scanning inodes on device /dev/rdsk/c1t1d0s6... ] > 04/01/2008 17:17:40 242 nVolumesInInodeFile 6776 ] > 04/01/2008 17:17:40 SALVAGING VOLUME 536870912. ] > 04/01/2008 17:17:40 Part of the header (Volume information) is corrupted ] ] Would need to try to fix header by hand if at all possible. Data on the ] disk is corrupted. ] ] > 04/01/2008 17:17:40 totalInodes 165 ] > 04/01/2008 17:17:41 "Salvage volume group" core dumped! ] ] Badly enough that the tools fail. If you have a core perhaps the tool ] can be patched to not crash.
/usr/afs/logs includes a corefile.fs from 3/31 but no (recent) core.salv and no cores from yesterday when the salvager ran. Any idea where it might be stashing cores? or how to force it not to delete them? ] There may be patches in 1.4.7-pre2 that might help. Let me know how I can use them. (I assume I get the 1.4.6 source and then find patches on the openafs site somewhere and apply?) John Boyland _______________________________________________ OpenAFS-info mailing list OpenAFS-info@openafs.org https://lists.openafs.org/mailman/listinfo/openafs-info