Re: GEOM and moving to CURRENT from 7.1

On Tue, Jan 13, 2009 at 4:35 PM, Ben Kaduk <minimarmot_at_gmail.com> wrote:
> On Tue, Jan 13, 2009 at 4:11 PM, Randy Bush <randy_at_psg.com> wrote:
>> installed amd64 7.1 from cdrom
>> partitioned two sata drives to single partitions
>> labeled and gmirrored
>>
>> upgraded to 8-current
>> ad0 started falling off mirror
>> ad2 started reporting smart errors
>
> Interesting.  I have been seeing similar behavior when trying to
> update my 7.1-prerelase box to current, except that it seems to be
> random _which_ disk falls off the mirror.  I'm also seeing panics if I
> try to stress the (then-degraded) mirror with the current kernel.  The
> mirror is rock-solid with the 7.1-pre kernel.
>
> The panic is "initiate_write_inodeblock_ufs2: already started", and
> I've got some details of the other messages I've seen logged up here:
> http://stuff.mit.edu/afs/sipb.mit.edu/user/kaduk/freebsd/periphrasis/20090107/panic.txt
> I just added a new swap device, so I'll see if I can actually get a dump once
> the mirror rebuilds.

Grr.  I built a kernel with WITNESS and INVARIANTS, and though I get
some (previously-reported, and apparently harmless) LORs on boot,
I can no longer reproduce the gmirror failure or the panic.

(The i/o scheduler is not too shabby, either, as I'm seeing something
like 20MB/s on each disk with four parallel bonnie++ processes.)

So ... a race condition, then?

-Ben Kaduk