The problem was the file server. Our guy who works on the file servers hasn't told the rest of us what happened, but I'll waterboard the guy if I have to and report back here.
I'm kidding about the waterboarding.
Sort of.
Maybe.
Anyway, this new cluster the board's on uses a Bluearc file server, and we've never used one before. Our file server guy went to Bluearc training for several days and we have a phenomenal support contract, so odds are what happened yesterday was a fluke and won't happen again.
I really need to read my email fully before commenting.
Anyhow, according to file server guy, the file server head crashed, and crashed spectacularly because it took him and Bluearc techs a couple of hours to bring it back up again. He's got a ton of diagnostic data to go over today to see what exactly happened, but I have a feeling it was something very odd.
Comments 2
I'm kidding about the waterboarding.
Sort of.
Maybe.
Anyway, this new cluster the board's on uses a Bluearc file server, and we've never used one before. Our file server guy went to Bluearc training for several days and we have a phenomenal support contract, so odds are what happened yesterday was a fluke and won't happen again.
Reply
Anyhow, according to file server guy, the file server head crashed, and crashed spectacularly because it took him and Bluearc techs a couple of hours to bring it back up again. He's got a ton of diagnostic data to go over today to see what exactly happened, but I have a feeling it was something very odd.
Reply
Leave a comment