I'd probably dig into why resize2fs says it's corrupt; large block should not mean corrupt, AFAIK, even if the running kernel can'tactually mount it.You might get this back on-list, too, so future generations can benefit from your pain (and in case someone else knows these answers).
Does anyone know if a 32k blocksize would cause resize2fs to report an invalid superblock? I've downloaded the source code and from what I can see the maximum block size is 64k, so I wouldn't have thought so - but I'm not a C programmer and have trouble following the source sometimes. I'd appreciate another set of eyes going over the code... Any help greatly appreciated.
David