On Sat, 2010-04-24 at 22:20 +0000, Steve Langasek wrote:
> Have I misunderstood the nature of this bug, or couldn't it be triggered by
> a flaky SATA cable causing intermittent connections to the drives? If one
> port flakes on one boot, the other port flakes on the next, and both ports
> are available on the third, wouldn't that trigger this same bogus
> reassembly?
Correct.
> So while it doesn't appear to be a recent regression, and not a
> high-frequency occurence, it does look like a data loss bug that can occur
> through no fault of the admin and I certainly think our users need to be
> warned of this in the release notes.
Indeed. I thought we had come to the conclusion that the language of
the release note was to be changed, not be completely removed.
On Sat, 2010-04-24 at 22:20 +0000, Steve Langasek wrote:
> Have I misunderstood the nature of this bug, or couldn't it be triggered by
> a flaky SATA cable causing intermittent connections to the drives? If one
> port flakes on one boot, the other port flakes on the next, and both ports
> are available on the third, wouldn't that trigger this same bogus
> reassembly?
Correct.
> So while it doesn't appear to be a recent regression, and not a
> high-frequency occurence, it does look like a data loss bug that can occur
> through no fault of the admin and I certainly think our users need to be
> warned of this in the release notes.
Indeed. I thought we had come to the conclusion that the language of
the release note was to be changed, not be completely removed.