I just had to share my awful experience I had today... when checking on the 11 gallons of Old Stock Ale I have been fermenting for a week, I noticed that there was beer leaking out very slowly from somewhere. It appeared to be the spigot. I turned it a little bit, hoping to stop the leak, and instead, the spigot failed completely - it was apparently shearing right in two.
So, I had beer spewing out from everywhere, and I grabbed the fermenter (a vittles vault that I had discovered has a small air leak somewhere around the rim, but that's another story...). I tipped the fermenter on its side, propped it up on its side to keep the beer from flowing out completely, slipping and sliding around in beer, trying to balance 11 gallons of liquid.
I somehow was able to get a 6 gallon bucket sanitized, trying to siphon out the beer from freshly exposed hole, which did not work very well. The only thing I could do was pull airlock off, empty it, plug a hose in to it, and turn the fermenter upside down while holding the stopper/hose assembly for dear life as it slowly flowed in to the spare fermenter.
Of course, everything was sanitized, and I flushed the new fermenter as well as I could with CO2. I got as much as I could in to this fermenter, without being close to done.
I decided instead of throwing out the remaining 3-4 gallons, I would go to the LHBS to pick up another 5 gallon bucket. The rest of the ordeal went somewhat smoothly (if you could describe a disaster as 'smooth'), and I was able to transfer the majority to the two fermenters, which are now bubbling away again.
Of course, this all happened the day before I am supposed to get three Speidel fermenters delivered.
I'm not too worried about an infection, I covered everything as it happened as well as I could with StarSan soaked paper towel... but oxidation is going to be the real test of whether this was a batch-killer or not.
Someone please tell me that I should be OK. I guess a couple of weeks from now it will be obvious, if there's any wet cardboard flavors going on... but I hope that's not the case.