ARRRRGH! Guys, who's breaking -STABLE's GMIRROR code?!

[Karl Denninger]

This is not cool folks.

Anyone know what I have to roll back to - and what files I have to roll back -
to stop this cluster-##@kery?

      tty             ad4              ad6            twed0             cpu
 tin tout  KB/t tps  MB/s   KB/t tps  MB/s   KB/t tps  MB/s  us ni sy in id
 224  453  0.61   0  0.00  120.16 427 50.06   0.61   0  0.00   2  0  4  2 92

See that?  There's nothing really running.  What I tried to do was 
"gmirror insert b500 ad4s1"

The command took, but NO IO WAS TAKEN TO THE TARGET DRIVE FOR REBUILDING; the
SOURCE disk was locked in a 100% I/O run, and after stopping the rebuild THE
I/O INFINITE LOOP IS STILL GOING ON!

I had a PRODUCTION MACHINE go down on my last night over this when it
attempted to run its backup process and wedged due to process table overflow;
the first attempt apparently never finished the day before and the second, to
a SECOND backup disk (I have a rolling disk backup system using GMIRROR's
resync) caused the system to wedge in an I/O wait.

This was also not cleanly restartable, as the root partition had multiple
error on it that fsck -p couldn't fix.

This is a SEVERE emergency in that anyone who has a disk that has to be
rebuilt under -STABLE right now (sources as of 7 September) is screwed, blued
and tattooed.

That PRODUCTION machine is running UNPROTECTED right now (no mirroring) as a
consequence of this, and I can neither back it up using the usual mirror NOR
restore its redundancy!

I see only one comment about GMIRROR changes in the commitlogs since 9/1, and
it claims to be (mostly) cosmetic.

Obviously not!

--
-- 
Karl Denninger (karl at denninger.net) Internet Consultant & Kids Rights Activist
http://www.denninger.net	My home on the net - links to everything I do!
http://scubaforum.org		Your UNCENSORED place to talk about DIVING!
http://genesis3.blogspot.com	Musings Of A Sentient Mind