What's actually on the filesystem. If your salvage deleted the files on the filesystem of the server there's no magic ...
What does your FileLog saying on start of the fileserver?
Anything like "couldn't attach volume ...."??
On Friday, April 23, 2004, at 06:31 PM, Forrest D Whitcher wrote:
I had a fileserver crash yesterday with apparently bad consequences.
The volumes are no longer listed in the vldb (I have a listing of ID's names etc but I'm not sure how much that helps.
command "vos listvol fileserver" gives:
Total number of volumes on server thing partition /vicepa: 0
Total volumes onLine 0 ; Total volumes offLine 0 ; Total busy 0
Total number of volumes on server thing partition /vicepb: 0
Total volumes onLine 0 ; Total volumes offLine 0 ; Total busy 0
Total number of volumes on server thing partition /vicepd: 0
Total volumes onLine 0 ; Total volumes offLine 0 ; Total busy 0
After the crash I stopped, then restarted all services on the fs, tho I have not yet done any restart on the database server.
post restarting services I ran a salvage, which ran fairly quick (3-4 min. on 2 4g and 1 8g partitions on a k7/600 system). I fear the speed with which this finished may well indicate the fs's view of what volumes it houses are well and truly lost.
the vldb showed the correct entries for a few hours after this fs crashed and restarted, I've tried to do the following to restore volumes that had been on the fileserver:
"vos syncv fileserver /vicepd 536870970"
So the question is, do I have any reasonable chance of recovering the currently invisible volumes on this fs?
If so, how should I be going about it?
thanks for any ideas
forrest _______________________________________________ OpenAFS-info mailing list [EMAIL PROTECTED] https://lists.openafs.org/mailman/listinfo/openafs-info
_______________________________________________ OpenAFS-info mailing list [EMAIL PROTECTED] https://lists.openafs.org/mailman/listinfo/openafs-info
