On 6/14/13 12:48 AM, Garance A Drosihn wrote: > On 6/13/13 12:33 PM, Andrew Deason wrote: > > On Wed, 12 Jun 2013 Garance A Drosihn wrote: > > > >> ... And am I right in > >> thinking that volumes shouldn't just show up as being > >> corrupt like this? Should I be looking harder for some > >> kind of hardware problem? > > > > Volumes shouldn't just show up as corrupt like that, yes. > > It now looks like it's a hardware problem with the SAN > storage for that viceb partition. Ouch.
We're still not sure what the initial hardware problem was, but whatever it was we got off pretty easy. After a long night, I had everything back up with very little lost. In fact, I'm not quite sure that anything was lost. In a quick look over the logs, I think almost all of the AFS volumes which were damaged by the Thursday night problem were RO replicas. And the end of all that, I have only two volumes which the file server process could not attach when I bought the file server back up. And those two were the two unused user volumes which started this thread. I'm inclined to go with 'salvager -oktozap' for those to volumes, and then restore them from backup. But I'm going to wait until Monday morning to do that. Thanks for all the replies! -- Garance Alistair Drosehn = [email protected] Senior Systems Programmer or [email protected] Rensselaer Polytechnic Institute; Troy, NY; USA _______________________________________________ OpenAFS-info mailing list [email protected] https://lists.openafs.org/mailman/listinfo/openafs-info
